Why Isn’t My Jira Automation Rule Transitioning Issues When Subtasks Are Resolved?

[Sophia Isabella]

Hey Atlassian Community,

I’m struggling with a Jira automation rule that’s supposed to transition a parent issue to “Done” when all its subtasks are marked “Resolved.” The rule seems set up correctly, but it’s not triggering, and I’m new to Jira automation, so I need some help debugging this.

Setup Details:

• Environment: Jira Software Cloud, latest version (as of July 2025), accessed via Chrome on Windows 11.
• Project: Scrum project, key PROJ, with standard issue types (Story, Subtask) and workflow (To Do → In Progress → Done).
• Automation Rule:
  • Trigger: Issue Updated (Subtask).
  • Condition: All subtasks of the parent issue have Status = “Resolved.”
  • Action: Transition the parent issue (Story) to “Done.”
• Issue: The rule doesn’t trigger when I resolve the last subtask. Automation logs show “No actions performed” or “Condition not met,” even when all subtasks are in “Resolved” status.
• Configuration:
  • Rule Scope: Single project (PROJ).
  • Condition: Uses “Related Issues Condition” to check “All subtasks” with Status = Resolved.
  • Actor: Automation for Jira (default).
  • Permissions: I’m a Jira Admin with full project access.
• Steps Tried:
  1. Verified all subtasks are in “Resolved” status via issue view—confirmed correct.
  2. Checked rule scope—set to PROJ only, no global rules interfering.
  3. Tested the rule in Audit Log—shows “Condition not met” despite subtasks being Resolved.
  4. Added a condition to check subtask count > 0—no change.
  5. Reviewed Atlassian’s automation guide (https://support.atlassian.com/jira-automation/docs/automate-your-jira-cloud-processes-and-workflows/)—followed setup steps.
• Expected: When all subtasks of a Story are “Resolved,” the parent Story transitions to “Done.”
• Actual: No transition occurs; logs indicate the condition fails.

Questions:

1. Why might the “All subtasks Resolved” condition fail, even when subtasks are in “Resolved” status?
2. Are there specific workflow or status settings I should check for subtasks?
3. Could project permissions or rule scope be causing this, even with admin access?
4. Any debugging tips for Jira automation rules that don’t trigger?

[Bill Sheboy]

Hi @Sophia Isabella -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

•  for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

If you are using the newer feature of adding conditions directly to the trigger, there are multiple reports of problems with that feature.  I recommend not using that feature and instead using individual field conditions.

Kind regards,
Bill

[Calvin]

• Condition: All subtasks of the parent issue have Status = “Resolved.”

Can you do a re-fetch action before this an see if you see a difference? I have a feeling the transistion is triggered but at that point of time the subtask is not yet closed until after the re-fetch of data.

Also if your triggering this in the subtask, are you then branching into its parent to transistion to solved/resolved?

[Sophia Isabella]

Hey @Calvin ,  

Thanks for the suggestions! I’m using a company-managed Scrum project, and yes, the rule branches to the parent Story to transition it to Done. I tried adding a re-fetch action, but moving the “All subtasks Resolved” condition out of the trigger (per Bill’s advice) fixed it—audit logs show it’s working now. I’m good to go, appreciate the help!

Cheers,
@Sophiaisabella