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; } } }

Can I set a delay in Jira Automation

James Woyciesjes

I am cloning an Epic and its Children using automation. I would like to remove a Label value from all of the cloned children.

If I have an Epic with one child, it works.

If I have an epic with many children, it seems that the processing is too fast. When that automation checks for the children, it sees none and ends.

Accepted answers

All comments

Oleksii Melnyk _MOY Apps_

Hi @James Woyciesjes

Снимок экрана 2025-07-22 214344.png
https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/

Oleksii Melnyk _MOY Apps_

Oh, but it's for Jira Coud(

James Woyciesjes

Thanks, I saw options for Cloud. In process of migrating but need something for the short term that doesn't involve a lot of coding, etc. if possible.

Trudy P Claspill

Hello @James Woyciesjes

Do I understand correctly that you are Cloning the issues in the first branch, and in the second branch you are trying to edit the issues created in the first branch?

If so, you will run into the problem that branches in Automation Rules execute in parallel. You cannot count on one to complete before the next one starts.

From this document:

https://confluence.atlassian.com/automation/branch-automation-rules-to-perform-actions-on-related-issues-993924648.html

Ordering of branch executions

Branches on multiple issues (such as 4 sub-tasks) will run in parallel with no guarantee one will finish before the next one starts. Therefore, you cannot rely on changes between branches.
Branches on multiple issues are run as a new process, with the main branch continuing execution before the sub-branch starts.
Branches on single issues are run inline (for performance). Therefore the main branch will not continue execution until the sub-branch completes.

To work around this you have to, even in Cloud, you have to split the activities of the second branch out to a separate rule, or incorporate the activities of the branches into a single branch, if possible.

Bill Sheboy

Hi @James Woyciesjes

Yes, and...to the suggestions from @Trudy P Claspill

I agree with using a single branch, and rather than copying all of the labels when the child issues are cloned, instead add the labels with JSON during the clone with the desired one already removed.

https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html

Kind regards,
Bill

James Woyciesjes

Thank you for the response, I will try and hopefully reply with success!

Aron Gombas _Midori_

You can always call an external service like this using the "Send web request" automation action:

https://httpbin.org/delay/5

It will sleep for 5 seconds. Easy.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center

jira-automation