Jira automation

[Suporte JRetail]

Is it possible to make rules activate in an sequence?

Is there any value that is changeable in order to make a queue of rules that act in an iten?

[Dirk Ronsmans · Accepted solution]

Hey @Suporte JRetail ,

There's no real sequence in the rules. If the trigger is the same they will all fire "at the same time" and you have no control over which one goes first/second.

With your case tho you'll have to either create a single rule that does all (cause in a rule it runs sequentially)

Or you need to set your triggers to (as @Mark Segall mentions to allow a trigger by other rules) but also to work with a field change from the previous rule.

E.g. if rule 1 changes the Client field then you can have rule 2 trigger on Issue Updated, Field Changed Client. ... 

Meaning the sequential logic between the rules, you'll have to create yourself.

[Suporte JRetail]

That was exactly what I wanted to do, Thaks @Dirk Ronsmans and @Mark Segall 

[Mark Segall · Accepted solution]

Hi @Suporte JRetail - Can you please provide an example of what you have in mind?  It is possible to have rules daisy chain off of each other by setting the Allow Rule Trigger, but it would be helpful to have more of an understanding of what you're trying to achieve.

[Suporte JRetail]

I have a rule that identify who is the client and another that based on the client, and another that assing someone based on customer.

And I need the first rule i said to go first and then the other one

[Suporte JRetail]

If you didn't understand something just let me know. (I actually don't manly speak english)

[Mark Segall]

I would look into whether it's possible to merge your three rules into one.  However, if that's not possible, you could do this...

Something I've done in the past is use a series of labels or components to drive a cascading set of rules:

1. At the end of rule 1, I apply a label like "Automation1" to the issue(s) in question. 
2. Rule 2 is set to trigger on field value changed (labels) and looks specifically for "Automation1".  At the end of that rule, the Automation1 label is removed and Automation2 is added. 
3. Like Rule 2, Rule 3 is set to trigger on field value changed (labels) and looks for "Automation2". At the end of the rule, Automation2 is removed

It's important to note that both Rule 2 and Rule 3 will fire twice each sequence (once when they meet criteria and once when they don't). So, you could run into throttling restrictions if this is something that will trigger with a high frequency.

[Suporte JRetail]

So merging isn't possible, but the second option will surely work, I will do that and that meet my goals, thank you very much.