The new automation feature that replaced triggers doesn't work so great

[John Jones]

In one of my Spaces (aka Projects), I set up some Automation rules that are meant to work like this:

• When a Work item (aka Issue) is transitioned from a specific step in my workflow to another, it checks "IF: Work item matched JQL "Team[Team]" = 192891f4-4523-31c7-ae7a-799f12375fbb-3 (let's call that non-user-friendly GUID, Team A, which is another bug I think Jira should address – see JRASERVER-79310), THEN: assign to Team A's Dev Lead.

Simply put, these are the conditions:

– If Team = Team A
----- then assign it to Greg (Team A's dev lead)
– If Team = Team B
----- then assign it to Joe (Team B's dev lead)
– If Team = Team C
----- then assign it to Bob (Team C's dev lead)

and so on...

This automation will correctly process the first condition, when Team = Team A, but does not continue through these If...then...Else rules when Team = Team B, C or D.

Why not?  Shouldn't it walk though this sequence of conditions from A to D?  ...but it doesn't.  The Work item only gets assigned properly when the very first rule meets the JQL passed in.

In short, I guess I'm trying to replicate a Case statement:

When Team = A THEN assign to Greg
When Team = B THEN assign to Joe
When Team = C THEN assign to Bob

Am I asking too much from Jira's new automation feature?

PS- the only "components" I can add in this new Automation feature of my Jira Space is (and in this order from the Jira UI):

THEN: Add an action

IF: Add a condition

FOR EACH: Add a branch

PLUS: Add an advanced component

[Bill Sheboy · Accepted solution]

Hi @John Jones 

For a question like this, context is important for the community to help.  Please post the following:

• what version of Jira are you using: Cloud, Server, or Data Center
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case 

Until we see those...

When using the if / else condition block in a rule, that would continue processing until a condition is met or the end, when none match.

When using other condition types, the rule will stop as soon as a condition is not met.

Kind regards,
Bill

[Mikael Sandberg · Accepted solution]

It would help if you included a screenshot of your automation, so my answer will be based on an assumption that you are using the if condition instead of if/else. If that is the case then it makes sense why the automation only works for Team A, because if you select Team B and using multiple if conditions it will stop on the first one since Team A is not selected. You should also be able to verify that by looking at the audit log to see where the automation stops.

[John Jones]

thanks for your replies.  I don't believe this new Automation feature offers an If/Else condition.  I'm on Cloud and here's the screen shot of the rule builder UI:



an If/Else component would be nice, but I don't see that as an option to chose from: