bj automation¶
Manage Jira automation rules (needs an unscoped Jira token).
Synopsis¶
Description¶
Jira automation rules. They live behind the Jira Automation REST API (api.atlassian.com/automation/public/jira/{cloudId}/rest/v1), not the platform API, and bj resolves the cloudId from the site for you. The rule endpoints need a Jira administrator, and Atlassian documents only unscoped API tokens for this API: a scoped token gets 401 scope does not match. If your login uses a scoped token, set BJ_JIRA_TOKEN to an unscoped one for these commands. export and import copy a rule: import drops the source rule's UUID, timestamps and component ids and creates the rule disabled unless you pass --enable.
Commands¶
| Command | Description |
|---|---|
list |
List automation rules (name, UUID, state, scope). |
view |
View one rule; --json prints its full definition. |
enable |
Enable a rule. |
disable |
Disable a rule. |
export |
Export a rule definition as JSON, ready for bj automation import. |
import |
Create a rule from an exported definition. |
delete |
Delete a rule. Jira only deletes disabled rules. |