Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Branch At Same Time not working with IF terms.

Matthew Chavan August 14, 2025

I have an automation setup to reopen requests when a customer comments, but I need to exclude a user set from this automation (i.e. user closes ticket and then comments should not reopen, etc.)

It seems that the IF condition is not matching as expected, but instead of stopping, the automation is continuing to run through the remaining branches.

 

In the screenshot of the audit trail, I would not expect the automation to continue past the yellow highlight because the work items did not match the condition. What am I missing here?Screenshot 2025-08-14 112313.pngScreenshot 2025-08-14 113905.png 

2 answers

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 14, 2025

Hi @Matthew Chavan 

First thing: I do not have a Premium license level and cannot test my suggestions.  My ideas are based on what I know about rules, in general.

Next, there is limited documentation on these very new features, none of which explain exactly what you asked.  And so to be absolutely certain, you could ask your Jira Site Admin to submit a ticket to the Atlassian Support team to answer: https://support.atlassian.com/contact/#/

 

My hypothesis for what you observe is: 

Although an advanced component (i.e., rule group) can take inputs and provide outputs to other groups, the processing and conditional logic stay inside of the group.

And so, that condition only applies to your "Exclude Treasury Comments" group.  The other rule groups on that same "User Comments" branch continue to process.

You could test this hypothesis by:

  • Invert the condition in that group
    • Using the result to set an Output value
    • Use the output value in the groups that follow
    • Although, that would be no different than just adding the condition at the top of each Reopen, Volley, etc. paths.
  • Or, remove that group and use the condition inline on the branch path (although I do not know if this is possible with the new features)

 

Kind regards,
Bill

0 votes
Mikael Sandberg
Community Champion
August 14, 2025

You are not missing anything, I have seen this happening on the conditions in the trigger as well. Check out the comments on this article that announced advanced branching. You should open up a support ticket with Atlassian so they can take a look at this. In my case because the conditions were ignored the automation I had generated over 4000 work items because the condition was ignored/bypassed before I disabled the automation.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events