Create
cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 
Sign up Log in

Automation - Trigger in Order

Mathew Lederman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 11, 2023

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.

1 answer

1 accepted

0 votes
Answer accepted
Esteban Diaz
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2023

Hi @Mathew Lederman , 

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

 

 subtasks.PNG

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:

component.PNG

looks like this:

subtask2.PNG

 

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2023

@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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2023

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:

Applied Systems - Procurement - Frame 1 (1).jpg

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2023

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.20.11
TAGS
AUG Leaders

Atlassian Community Events