Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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:

 

image.png

2 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 :)

Ste

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,

Bill

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,

Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

248 views 2 1
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