Create a Jira automation rule
A useful first automation rule removes one repeated administrative step and is easy to audit. Jira’s new interface calls these rules flows. Every flow has a trigger, optional conditions, and actions. Start small, test it on one work item, then turn it on.
Company and team-managed spaces
The flow builder is the same in both space types. Start in the space when the automation should only touch that space's work. A Jira admin can create global or multi-space flows that include company and team-managed spaces.
-
Open Automation and create a flow
Next to the space name, select More actions (•••) → Space settings → Automation. Select Create flow → Create from scratch, or choose a template. -
Choose one trigger
For a first rule, use Work item transitioned, Work item assigned, or Scheduled. A trigger is the event that starts the rule. -
Add a condition when it prevents noise
For example, limit a transition rule to Work item type = Sub-task. Conditions stop the action from running on work that merely shares the same event. -
Add the action and test it
Use Add step to add an action such as Transition work item or Assign work item. Test it with a deliberately named work item before enabling it for real work. -
Set the flow details and turn it on
Select Flow details to name the flow and check its scope, then select Turn it on. Check Status in the automation audit log after its first run to see which work items it handled and why an action failed.
Good to know
Three first rules that are useful without being risky:
- Close the parent when every subtask is done: Trigger: Work item transitioned to Done. Condition: work item type is Sub-task. Branch: Parent. Re-fetch work item data, then check that all subtasks match Done. Action: transition parent to Done.
- Assign new bugs to triage: Trigger: Work item created. Condition: work item type equals Bug. Action: assign the triage user or team.
- Close stale work on a schedule: Trigger: Scheduled, with JQL
status = "Waiting for review" AND updated <= -14d. Action: transition work item to Done. Test this one especially carefully. - The flow actor needs permissions. Automation can only do what its actor is allowed to do in the affected space.
- Transitions must be valid. An action cannot jump a work item to a status its workflow does not allow; the audit log will show the failure.
- Scheduled rules with a JQL query act on every matching work item. Keep the query narrow and re-run it manually before enabling the rule.
Give the team a calmer board
Automate the repetitive step, then keep the remaining work visible and easy to act on.
FAQ
What are the three parts of a Jira automation rule?
A rule starts with a trigger, can use conditions to narrow which work items continue, and finishes with one or more actions.
Why did my Jira automation rule fail?
Open its audit log. Common causes are an invalid workflow transition, a missing required field, or an automation actor without permission in the affected space.
Can a scheduled Jira automation rule use JQL?
Yes. Add a JQL query to a Scheduled trigger and Jira will run the rule's actions on matching work items.