-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: Conditions
Since I can't create a bug nor make a support request (JRASERVER-79311), I guess I'll make "suggestion": your new automation feature that replaced triggers doesn't work so great!
In one of my Spaces (aka Projects), I set up some Automation rules that work like this:
- When a Work item (aka Issue) is transitioned from a specific step in my workflow to another, if checks "If: Work item matched JQL "Team[Team]" = 192891f4-4523-31c7-ae7a-799f12375fbb-3 (that team's global ID, which is another bug I think you should address – see JRASERVER-79310 – but let's call that non-user-friendly GUID, Team A for this example.
so the conditions are:
– 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 get 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?
- links to