Transition a Sub-Task when another Sub-Task type is moved to Done

[Lesly Cracchiolo]

Howdy!

I have been trying to create automation for the following:

• Story Issue has 3 different Sub-Task issue types:
  • QA Task
  • Dev Task
  • UI Task
• When the Dev Task transitions to DONE I would like the UI Task to transition to "Ready for UI"
  • In the workflow, ALL statuses may transition to this status.

Hoping someone can help me out with this. It seems simple, but I have really been struggling. 

Thanks in advance!

[Bill Sheboy]

Hi @Lesly Cracchiolo 

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

• 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

Kind regards,
Bill

[Lesly Cracchiolo]

Thanks, Bill!

• Jira Cloud - company managed
• I have tried SEVERAL options and none of them work so I am hoping someone can help me from scratch.

Expected behavior: When the Dev Task (Sub-Task type) is transitioned to Done I would like another the UI Task (Another Sub-Task type in the same story) to automatically transition to Ready for UI.

My workflow allows for this transition in both cases, I just cannot get the automatic trigger to work. 

[Bill Sheboy]

Seeing what you tried will help to rule out (no pun intended) potential problems and identify what prevented the rule from working.

The most basic rule to do this would be:

• trigger: work item transitioned to "Done"
• condition: work item type is "Dev Task"
• branch: on JQL to the other sub-task -- parent = {{triggerIssue.parent}} AND issueType = "UI Task" AND status != "Ready for UI"
  • action: transition to "Ready for UI"

[Lesly Cracchiolo]

Thank you again for helping me out! Using your advice this is what I get:

[Trudy Claspill]

Hello @Lesly Cracchiolo 

Bill has jumped in to help with posts I've been answering before, so I am going to return the favor.

Your first problem is that with the branch you are changing the focus of the rule from the subtask that triggered it to that subtask's parent. Then you have a condition to see if the issue now in focus (the parent) matches the JQL you specified, which it will never do.

parent={{triggerIssue.parent}}

... is check if the issue in focus (the subtask Parent) itself has a Parent that matches the subtask's parent. To match this, the subtask's Parent would have to be its own Parent.

Instead use a For Each: Related Work Items: JQL branch.

Use the same JQL that you put into the condition. That will cause the focus to change to any work items that are siblings of the subtask (same Parent) that are also of the correct type (UI Task) and in the correct status (anything except Ready for UI).

Remove the Condition from within your branch.

And then your rule should work.

[Lesly Cracchiolo]

Hi Trudy,

Thank you for your help! I'm having some trouble completely understanding what you said above. Can you put it into steps for me, please? =)

What do I do next? 

[Lesly Cracchiolo]

This is also not working

[Bill Sheboy]

Please see my earlier post above ^^^

• remove the JQL condition you have
• and instead use the Branch rule / related issues
  • select the type as JQL
  • use the JQL you currently have in that condition
  • disable the option to "Only include work items that have changed since the last time this rule executed"
  • ensure the transition action is inside of the branch

[Lesly Cracchiolo]

I was able to get it! Thank you both for your help!!!!

This is what ultimately worked:

[Trudy Claspill]

Change the work items types and statuses to match your scenario. Use the JQL you have, not the one I've put into my example.