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.
