Automation - Trigger in Order

[Mathew Lederman]

Is there a way to force the order for Project Automations to trigger?

Backstory: We have built our IT service desk in Jira and we are heavily dependent on Project Automation.

Example: New User

• Creates Sub-task A when the request is approved
• Creates Sub-tasks B-E when Sub-task A is resolved
• Creates Sub-task F based on the answer provided on the resolve screen of Sub-task E

As you can see, this is highly customized and highly dependent on the automation.

One of the cross-project pieces of automation is to resolve the parent task when all sub-tasks are resolved. 

Unfortunately with some request types Resolve Parent when Children Resolve automation is kicking off before Create Sub-task E, so we end up with a Resolved parent and a new Open sub-task.

How can we force the Resolve Parent automation to trigger absolutely last?

I tried a simple rename and renamed the Automation to zResolve Parent thinking it might kick off in alphabetical order, but that didn't work.

[Esteban Diaz · Accepted solution]

Hi @Mathew Lederman , 

I'm using an automation that looks like this one:

I Have a Parent Task and many possible subtasks (Phone, Hardware or Email) This automation is triggered each time any subtask is transitioned to Close or Rejected statuses. Then I created a Branch (For: Parent)  where if all the related subtasks get into Closed or Rejected status, then transition the Parent issue to Resolved The component: looks like this:

Maybe this approach could be useful for you....

I will be waiting for your comments. 😉

Cheers!

Esteban Diaz
https://www.linkedin.com/in/estebandiaz/ 

[Mathew Lederman]

@Esteban Diaz appreciate the recommendation, we have something very similar. The problem is that sometimes it kicks off before other automations that create subtasks based on the resolution of a previous sub-task. Both pieces of automation trigger off the same circumstance, issue transitions to resolved. I need a way to choose in which order the automations trigger.

[Esteban Diaz]

Hi @Mathew Lederman , 

I had a case where I needed to fire automations in order, and to solve it I created a custom filed to be used like a flag and when the flag changes the second automation reacts.

something like this:

Automation A updates the custom field  CF_FLAG value on Issue XX-1

Automation B is listening for any value change on CF_FLAG custom field and if CF_FLAG change and is True, then Creates a new ISSUE XX-2

Does it makes sense? 

Esteban Diaz
https://www.linkedin.com/in/estebandiaz/ 

[Mathew Lederman]

Esteban,

That does make sense, unfortunately this doesn't really solve the issue. The automation to set the flag would be the same automation that checks if all sub-tasks are resolved. It would result in the same issue unless I'm misunderstanding.