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?
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:
Kind regards,
Bill
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.