Automation Condition passing even if not true

[Niklas Zarnecke]

Hey,

I'm currently stuck on a problem with one of our automtions in Jira. Here is the entry in the audit log:

When I'm looking in the history of the Story, I can see that the Story is in the status "ON STG" since the 26th of Novemeber 2024:

So in my logic there shouldn't be any execusion of the rule, why does it try to move the Story any way?

Here is my config of the automation:

Thank you!
Niklas

[Mohamed Benziane]

Hi,

you're using the parent branch so it seems that the trigger issue is a subtask of the story .

basically your rule is, when an issue is transitioned and it has a parent then make a transition in the parent.

[Dick]

@Niklas Zarnecke :

• Your consecutive conditions always prohibit execution of the last condition. An if-block can help you out in this situation.
• best verify the issuetype of the triggerissue first, to avoid doing stuff on stories and epics (also a child parent situation).

Kind regards,

Dick

[Niklas Zarnecke]

Hey @Mohamed Benziane @Dick

I'm trying to move the parent (standard task) when all the sub tasks are in the same status. The first check if all sub tasks are in the same status seems to be working but the second check if the parent already is in the same status is not working the way it should.

The automation always moves the parent, even if it already reached the right status.

Best
Niklas

[Dick]

What if one subtask is ahead and the remainder is all on one status?

Could you be "saved" by looking up the status of the task that is least progressed in the order of statuses in your project ? Said order should be "known" in the automation.

That would require a totally different approach from your original plan.

Kind regards,

Dick

[Niklas Zarnecke]

Hi @Dick ,

now that I'm thinking about that, it really sounds better that way.
I totally missed the point, that we could get some inconsistencies that way.

I will have a look into that.

Best
Niklas

[Vishal Biyani]

@Niklas Zarnecke 

I relooked at your problem statement and this is my understanding.
You have a story or Task and n number of subtasks under the Story/Task.
Let's say all of them are in To DO status.
Team will transition the status of subtask and if all subtask have same status say In Progress then automation should trigger and update the status of Story/Task.

This is the rule I propose

• Trigger: Issue Transition
• Check if this is a subtask using JQL: issuetype in subTaskIssueTypes()
• Add a lookup: parent = {{ triggerIssue.parent.key }}
• Create a smart variable say subtaskStatusCount to Count the unique status of subtask: {{lookupIssues.status.name.distinct.size}}
• Check if subtaskStatusCount = 1 [This means all subtask have same status ]
• Create smart variable subtaskStatus and save the status of triggerIssue: {{triggerIssue.status.name}}
• Branch to Parent
• Check if {{issue.status.name}} does not equal subtaskStatus 
• Transition the issue: Copy from trigger Issue.

Let me know if this works for you

[Duc Thang TRAN]

Hello @Niklas Zarnecke 

Your requirements still need more details. However, after analyzing your screenshot, there might be some inconsistencies.

Which type of tickets are you targeting? Sub-task, standard task, or epic?

[Niklas Zarnecke]

Hey @Duc Thang TRAN ,

when all my sub-tasks are in one status the parent should be moved as well.

It seems like the first check is working but the automation trys to move the the parent (standard task) anyway, even if the parent already reached the right status.

[Vishal Biyani]

@Niklas Zarnecke 

Before branching into parent, can you try copying the trigger Issue values in smart variable. Then use those values to compare with parent status.

See if this helps resolve your issue.

[Niklas Zarnecke]

Hey @Vishal Biyani

thank you, I will try that!

Best
Niklas