Sub-tasks not transitioning parent ticket based on sub-task status

[Mahnoor Arshad]

I have a radio button custom field as 'ML Approvers' that has four options (Ep1 Space CR, Ep2 CR, Ground CR, Integration CR). The value 'Integration CR' is the default value for the custom field so it is already preselected. 

Based on the ML Approvers selection, a subtask is created for each value that is selection i.e., if Integration CR is selected then a sub-task is created and linked to the parent ticket. 

I built out an automation rule that checks that each sub-task is in the status 'Concur', or 'Not Applicable' which should then move the parent ticket to the status 'Approved'. 

However, once the 'Integration CR' was set as a default value. It broke the automation rule and is no longer executing properly. Can someone please assist in how I can modify the workflow to have it run as it is intended. I have included screenshots for reference.

Custom field:

Automation Rule:

[Bill Sheboy]

Hi @Mahnoor Arshad -- Welcome to the Atlassian Community!

Please explain what you mean by "is no longer executing properly". 

Specifically, what do you observe happening and when / what steps proceeded that behavior?

And for more context on what you are observing, please post images of:

• your condition in the branch which checks the subtasks status
• the audit log details showing the rule execution

Kind regards,
Bill

[Mahnoor Arshad]

Hi @Bill Sheboy, 

The automation rule included as a screenshot in this thread was working as intended. Transitioning the parent issue to 'Approved' when the sub-task would go into the status 'Concur' or 'Not Applicable'. 

However, once the ML Approvers custom field set 'Integration CR' as a default preselected value the same automation rule stopped working. Which I believe is what is causing the rule from not transitioning the parent issue to the status Approved. 

The audit log keeps saying that the 'Related issues condition' did not match the issue. So not sure what keeps on preventing the automation from executing the intended rules. 

Error Screenshot: 

[John Funk]

HI Mahnoor - Welcome to the Atlassian Community!

That tells me the parent status is not equal to Approval at that point. You can log the current value out to see if you want, but that's the error message to me. 

[Bill Sheboy]

@John Funk -- I believe the log now shows the Parent matching and the Subtasks not matching the JQL.  Perhaps one of the earlier post's edits showed it the other way?

@Mahnoor Arshad -- without seeing image for the condition I asked about...

First, you seem to be using Jira Server or Data Center.  Is that correct?

Next, it appears you are using the "All match specified JQL" option.  In my experience, the related issues condition (particularly with JQL) can have some odd behaviors. 

With your current rule, let's verify what is happening by adding a write to the audit log with the Log action, inside the branch and before Subtasks check:

subtasks: {{#issue.subtasks}}{{key}}:{{status.name}}; {{/}}

This should list the subtasks with their status names, helping to verify your assumptions.

FYI -- Because of the occasional odd behaviors I described with that condition type, a workaround is to not use it, and instead use the Lookup Issues action and a Advanced Compare Condition.  For example, the JQL can be inverted to check for the absence of other issue status values:

• ...
• Branch: to parent
  • Issue Fields Condition: status equals Approval
  • action: Lookup Issues, with JQL to check for issues not in the desired status
    • parent = {{issue.key}} AND status NOT IN ("Concur", "Not Applicable")
  • Advanced Compare Condition:
    • first value: {{lookupIssues.size}}
    • condition: equals
    • second value: 0
  • action: Transition Issue to Approved

[Mahnoor Arshad]

@Bill Sheboy & @John Funk 

I was able to figure it out. The automation rule needed 'Done' added to the transitioned trigger issue. Because there is a subtask that moves to the status 'Done' it checks that for the parent issue. It is now working as needed.

Thank you both for your input, it was well appreciated! :)