Automate Jira Status Transitions with Cloud Automation Rules

Desired Outcome

Automatically move issues from one status to another based on defined business rules, eliminating manual status changes and ensuring a consistent workflow.

Prerequisites

• Jira Cloud instance (2024.6 or later).
• Project with a workflow that includes the target statuses.
• Project Administrator or Automation Admin role.
• Rule owner must have the Transition Issues permission for the target status.
• Optional: Test project for trial rules.

Focused Procedure

1. Open Project Settings

   Navigate to the target project, click Project settings > Automation. Click Add rule to start a new rule.

2. Define the Trigger

   Choose Issue transitioned as the trigger. Set the From status to In Review and To status to Ready for QA (example values).

3. Add a Condition

   Click New condition > Issue fields condition. Set Field to Resolution, Condition to Equals, Value to Won't Fix. This ensures only issues resolved with that resolution trigger the transition.

4. Add the Action

   Click New action > Transition issue. Choose the target status Done (must be reachable from the current status in the workflow). Optionally, set Send email or Assign user actions as needed.

5. Name and Save

   Give the rule a descriptive name, e.g., Auto‑Done on Won't Fix. Click Save and then Turn on to activate.

Expected Checks

• Open an issue and transition it to In Review then resolve it with Won't Fix. Verify that it automatically lands in Done and that the status history reflects the transition.
• Navigate to Project Settings > Automation > Audit Log. Confirm a successful execution entry with no errors.
• Check that the rule owner’s permissions allow the transition: go to Project Settings > Permissions > Issue Permissions and verify Transition Issues for the target status.

Recovery Options

• Disable the rule: In the rule list, toggle the switch off. This stops further automated transitions.
• Delete the rule: If the rule is no longer needed, click Delete from the rule details page.
• Re‑enable after testing: Once you confirm the rule works correctly, toggle it back on.

Common Pitfalls & Mitigations

• Infinite loops: Avoid rules that trigger on the same status change they perform. For example, a rule that moves from In Review to Open and another that moves from Open back to In Review can cause endless toggling.
• Performance impact: On large projects, overly frequent triggers can slow down issue loading. Use Scheduled triggers sparingly and target specific issue types.
• Security exposure: Since the rule runs as the rule owner, ensure that the owner’s role does not have excessive field‑level permissions that could expose sensitive data.

Limitations & Verification

• Automation rules cannot transition an issue to a status that is not reachable in the current workflow. Verify the workflow diagram before creating the rule.
• Audit logs provide a record of rule executions but do not capture field values unless you explicitly log them via the Set field value action.
• Rule execution is asynchronous; status changes may appear a few seconds after the trigger. Use the Issue history tab to confirm the timing.

Practical Example: Auto‑Close Bug When No Fix Is Planned

Suppose you want bugs that are marked Won't Fix to automatically close. Create a rule with the trigger Issue resolved, condition Resolution equals Won't Fix, and action Transition issue to Done. After enabling, resolve a test bug with Won't Fix and confirm it lands in Done and the audit log shows a successful run.

Conclusion

By carefully defining triggers, conditions, and actions, and by validating permissions and audit logs, you can create reliable, automated status transitions in Jira Cloud that keep your workflow consistent and free from manual overhead.