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

[Corinne Guibert]

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

[Marc -Devoteam-]

Hi @Corinne Guibert 

My fellow community members have solid points and information. 

Thanks @Fazila Ashraf and @Nikola Perisic 

But why don't we look if these automation can't be combined in a single rule.

So based on the trigger fields are updated, then add a re-fetch action or a delay and then based on probably a condition assign the issue?

Would be helpful if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

[Bill Sheboy]

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

[Corinne Guibert]

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]

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? 

[Fazila Ashraf]

Hi @Corinne Guibert 

Generally the automation run async and there is no way to simply reorder the execution sequence of all of them. I have worked around important exceptional automations through webhook relays. Screenshots below to help with the general idea. Hope this helps!

[Nikola Perisic]

Hi @Corinne Guibert 

You might find these helpful:

https://community.atlassian.com/forums/Jira-questions/Sequence-of-execution-of-automation-rules/qaq-p/2517434

https://community.atlassian.com/forums/Jira-questions/How-to-Control-the-Execution-Order-amp-track-changes-of-Jira/qaq-p/2963676