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: When all sub-tasks are done → move parent to Done

I am trying to configure the rule "When all sub-tasks are done → move parent to Done". However, faced some troubles. Firstly, in the audit "no actions performed" message appeared. Secondly, when all subtasks are transitted to "Done", the message "Update Parent Issue" is triggered. Is there any mistakes in the rule or maybe something else causes the issue?photo5246924983475745712.jpgphoto5246924983475745714.jpgphoto5246924983475745717.jpg

4 answers

4 accepted

2 votes
Answer accepted

Hi @Alexey Petenko  -- Welcome to the Atlassian Community!

For your question about why no actions are performed...

Your trigger checks for a sub-tasks moved to the "Done, QA" status, but later you test a condition for all sub-tasks moved to the "Done" status.  So those cannot match.

If you have multiple possible "done" status values for sub-tasks, perhaps your "If sub-tasks match" condition should test for all possible "done" status values.  For example:

status IN ("Done", "Done, QA", etc.)

Also, I recommend adding another condition prior to transitioning the parent, checking first that it is not already in "Done".  That will prevent repeatedly moving of the parent to that status.


Best regards,

Bill

0 votes
Answer accepted
Jack Community Leader May 11, 2021

What status is the parent in And is there a supporting transition from the current status to done? In other words once all of those subtasks are done and the parent fails to be moved to done by automation can you manually move the parent done?

It is not important is which status the Parent is, however, typically it is either in custom status "Approved" or "In Progress" (mostly).  Yes, manually the Parent can be transited in "Done" (screenshot above).

Also, we have the second rule where the parent is transited to "In Progress" and this rule is fine.

We aim to make 2 separate automation rules or one - "When the first sub-task is moved to "In Progress" --> Parent is moved to "In Progress" and when all sub-tasks are moved to "Done" --> Parent goes to "Done" automatically. 

0 votes
Answer accepted
John Funk Community Leader May 11, 2021

Hi Alexey - Welcome to the Atlassian Community!

That message looks like it comes from the workflow itself. Is there some type of post function on the workflow in addition to the automation rule? 

I cannot clearly understand what do you mean, therefore, can you please clarify the cause with the workflows.

Also, there was a mistake in the screenshot above, Parent issue is transitioned to both "Done" and "QA"

done and qa.JPG

John Funk Community Leader May 11, 2021

You have to edit the workflow itself - not the automation. 

Got to Settings > Issues > Workflows

Search for the workflow being used by the project and click on Edit

It might be a workflow specifically used by sub-tasks so be sure you have the right workflow. 

Then click on the transition to Done. 

Finally check the post functions on that transition to see if there are any for Transition parent issue - or something like that. 

John Funk Community Leader May 17, 2021

Hi @Alexey Petenko  - Have you done these things? 

0 votes
Answer accepted
Yvan Martin Atlassian Team May 13, 2021

Hi there,

Developer from Automation here.

In general your rule looks correct from a sync sub-tasks point of view, we have a very similar rule available in our template: library https://www.atlassian.com/software/jira/automation-template-library/most-popular

As others have mentioned though your trigger status has QA listed, but you don't look for QA in sub-tasks, you might need to adjust this or what status is considered done in your definition.

If you require further help more specific to your instance than it's worth getting in touch with support here: https://support.atlassian.com/

The thing is that when all sub-tasks are transferred to Done, they literally go to Done. However, when Bug sub-tasks are transferred to Done, they change their status to QA

photo5264830856751591844.jpg

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 Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

263 views 7 7
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