Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation Rule error - Close sub-tasks when Parent transitions to Done

My goal: Create an automation rule to close all sub-tasks in a story when the Story issue is closed.

I get an error in the audit log after running. I've attempted many tweaks but the error message is always the same and I'm in need of another set of eyes.

Audit Log Error: 

Action details:

Transition issue

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):AR-903 (To Do/Backlog - 10002)

Here is my Rule:



3 answers

Hi @Kirk, Becky 

The rule itself looks fine. 

For this error, simple first checks can be to see if there is a restriction or limitation in the workflow stopping automation from closing the sub-tasks - for example:

  • Does the status "Completed" exist in the sub-task workflow?
  • Can all other statuses transition directly to "Completed" - i.e, if you don't have an open workflow (where all statuses can transition to all other statuses), then some sub-tasks might not have an option to transition straight to "Completed"
  • Does closing a sub-task require a specific field to be filled in - such as a resolution? Are you setting the resolution in this automation rule?
  • Is there a workflow condition for transitioning to done - such as it must be the Assignee?

^ Checking out the workflow and what might be missing from the rule will help decipher if this is just a tweak to the rule, workflow - or both!

If all of these check-out, let us know so we can advise further :)


Hi @Kirk, Becky 

In addition to what Stephen suggests...

Please consider adding a Condition after the Trigger and before the Branch (For Sub-Tasks) to confirm that the issueType matches what you expect: Story.

Best regards,


Hey, @Stephen Wright _Elabor8_ - I have the same error. I have set the resolution to done when sub-tasks are moved to done. This works fine. The issue I'm having is when all the sub-tasks are moved to done then the story itself doesn't close and the automation rule fails. I'll share the automation rule details and the workflow details as well. 


Looking Forward. Demo Workflow.pngAutomation Rule.png

Hi @Hizkeel Khan 

I recreated this rule and it works for me.

Is that Workflow above for Sub-tasks or Stories?

I'd be checking...

  • Workflow: If that is the Story's Workflow, or it has similar single transitions - the Story would need to be in Ready for QA to progress to Done using this rule. Is that the case?
  • Resolution Screen: If the Story's Workflow has a Resolution screen, thus requiring a resolution at closure, rather than a post-function to set Resolution. If it does, you'll need to set the resolution during the transition action.
  • Rules: Ensure the Story Workflow has no other conditions, validators, etc related to transitioning to Done which you haven't factored into the rule.

If none of these are the issue, could you provide a screenshot of this rule's audit log - in particular, what error it provides when it fails?


Like Bill Sheboy likes this

Hi @Stephen Wright _Elabor8_ - Thank you for your reply. The workflow is same for story and sub-tasks. 

For Resolution, I have created and added a post-function that whenever a sub-task is moved to done status. a strikethrough appears on the task confirming that the sub-task is completed.  

I have added some validators and conditions but I don't think it should affect the automation rule I have applied. 

Of course the story can't move to done status unless all the sub-tasks under that story are completed and moved to Done but as soon as my sub-tasks are moved to Done Status, my story should close automatically. 

Opps..wrong thread I posted in

Hi @Mayur Patankar 

Did you post this one in the correct thread?  That suggestion seems unrelated to the question about an automation rule closing sub-tasks.

Thanks, and best regards,


Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

1,364 views 10 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you