nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wait until other active automations are finished processing

Benjamin Høegh

There is this template that Atlassian so kindy have made for us, there cloeses the parent when all sub-tasks i closed. Works great

The issue is when haveing a sub-task there generate new subtask in the parent when finished the other automation gets triggered before it's done creating new sub-task resulting in the parent task is closed while the new subtaks still gets created, this result in the parent being closed but have open subtaks

is there a way to prevent this?

Accepted answers

All comments

Sayed Bares [ServiceRocket]

@Benjamin Høegh It is not possible to wait or stall the automation there is a feature request which may address your question https://jira.atlassian.com/browse/AUTO-238.

What I would suggest as an alternative is to create another automation which will open the parent if a new sub-task is added.

Benjamin Høegh

Will that not result in new notifications for the assinged user?

Sayed Bares [ServiceRocket]

@Benjamin Høegh that depends on your project's notification scheme.

If you are using the default one then yes All Issue watchers, Reporter and Assignee will be notified

munir ashraf

Hey there,

Munasir here, I've run into similar automation hiccups with Atlassian tools before. 😅

It sounds like you're in a classic race condition where one automation is triggering before another finishes. You might want to consider adding a delay or setting a condition for the parent-closing automation to check not just for existing sub-tasks but also any "in progress" sub-task creation processes.

Or better yet, if possible, adjust the sequence of automation such that new sub-task creation happens before the parent issue evaluation. It's a bit tricky, but playing around with the automation sequence might just do the trick.

Would love to hear if anyone else has found a smooth workaround for this!

Keep coding and configuring!
Munasir. 🚀

Bill Sheboy

Hi @Benjamin Høegh

As others have noted, this symptom is possibly caused by a race-track condition spanning your rules. Often the solution for this is to change your approach. For example, collapsing multiple rules into one, changing rule triggers, etc.

To help with that, the community will need to see images of your complete automation rule, showing all details of the actions, and of the audit log details showing the rule execution. Those will provide context for what adjustments can be made.

In the meantime, would you please explain the problem your rules are trying to solve?

You initially state this is to close the parent when all subtasks are closed...However, you later add more subtasks are created, which seems to indicate either a process problem or the rules do more than what you indicate.

Kind regards,
Bill

Sajid Ali_vsmz7l

thank, i will do also

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management