Automation (flow ?) : what is the execution order ?

Question

Hello

I have several automation. One of them us updating some fields (if they have not been set from the ticket creation)

The other one is assigning the ticket based on the fields value

Is there a way to make sure that the automation that updates the fields is triggered before the one that assign the ticket ?

Il would like to avoid duplicating the assignation steps in 2 different automations

Thanks for your feedbacks

Bill Sheboy · Answer

Hi @Corinne Guibert -- Yes, that sounds correct, and...

By default, the actions of one rule do not trigger other rules.  That prevents accidental, runaway rule looping!

When you intentionally want the actions of one rule to trigger another, in the second / downstream rule, enable this option in the details at the top: "Check to allow other flow actions to trigger this flow..."

Thus your rules could be:

* rule A:* global rule, triggered on work item created,
* with the option probably disabled for "Check to allow other flow actions to trigger this flow..."
* immediately after the trigger, I would add the Re-fetch Work Item Data action before any steps to prevent racetrack timing problems
* continue with your steps to set the "Origin Region"...

* rule B:* space-scoped rule in your new Team-managed space, triggered on a change to the "Origin Region" field,
* with the option enabled in the details at the top
* using the field, make the assignment, and...
* question: what do you want to do if the work item was already assigned when this rule starts?

Corinne Guibert_lao912 · Answer

Hello  @Marc -Devoteam- , @Bill Sheboy

I gave a global rule (used  in many spaces) that assigns the  field "Origin Region" to a specific value based on the reporter when the ticket is created

In a new team-managed project, I need to Assign the ticket based on the "Origin Region" field. that's why I need to make sure that the first rule is executed after the global one.

But maybe I need to run the  Assignement rule using a different trigger: instead of ticket creation, it would be when the Origin Region is filled

Bill Sheboy · Answer

Hi @Corinne Guibert

Yes, and...to the suggestions from @Marc -Devoteam-

Seeing the specifics of your rules and what problem they are trying to solve (i.e., the "why" for each rule), may reveal an opportunity to either:

* merge / re-organize some rules
* change the rule triggers such that the actions of one rule lead to trigger later ones in the "chain" of flow

Kind regards,
Bill