Ability to update a related Sub-Task based on the Status of another Sub-Task

[Steve Huffman]

I am trying to figure out a way to automatically update the status of a Sub-Task based on a Status change of another Sub-Task under the same parent.  For example:

• Story
  • Generate Code Merge Sub-Task
  • Merge Validation Testing Sub-Task

The Generate Code Merge Sub-Task is manually moved from In Progress to Done.  Automation updates the status of the Merge Validation Testing Sub-Task from Open to Ready.

[Trudy Claspill · Accepted solution]

Hello @Steve Huffman 

Are the Summaries for these related subtasks fixed? Will it always be that when a subtask with summary = "Generate Code Merge Sub-Task" is transitioned then you will want to transition its sibling subtask where summary = "Merge Validation Testing Sub-task"?

Will there ever be more than one subtask that contains the text of either of these Summaries?

You could accomplish this with a rule structure thus:

[Steve Huffman]

Thank you.  This got me much closer than I was when I started.  I can get the above to execute, but it is not changing the status of the secondary sub-task.  Below is what I set up.  Is there something I am missing I am not seeing?

NOTE: To answer your question regarding if the names are fixed, I am using the names as prefixes and then appending the parent name to the end.  I am using another automation to generate the two sub-tasks.

Example

- Generate Merge Request_Parent Story Name

- Merge Validation Testing_Parent Story Name

Here is my automation.

[Trudy Claspill]

Review the Audit Log for the Rule.

Is the overall status for execution entries "Success" or some other value? 

If you click on the Show More link next to one of those Success-ful executions, what are the details for that execution?

[Steve Huffman]

The audit log shows a "No Actions Performed" response.  In the image below, the DAT-1035 issue is the "Generate Merge Request_" task.

If I change the Branch from parent = {{issue.parent.key}} to parent = {{issue.parent}}  the result is the same; however the audit log status changes to "Success"

[Trudy Claspill]

Notice the last message.

No related issues that have been updated since the last time this rule executed could be found.

When you create a For Related Issues/JQL step there is a checkbox that is checked by default that will further constrain the selected issues to only ones that have been updated since the last time the rule executed. Uncheck this box and see if that makes a difference.

[Steve Huffman]

That fixed it!  Thank you!!!