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

Automation Error with sequential tasks

Sophia Skinner_ojvlrb

Hello Atlassian community!

I have a semi-failing automation with no clear explanation.

To set the scene here: I am attempting to create a rule to auto populate tasks based on epic with tasks following sequentially from the epic due date. This is sort of working.... it will sequence the first 7 tasks in the correct order, but will not complete the remaining 4. The Epic still displays the proper duration as if these were included though. Attached are some screenshots of the timeline and an example of how I configured the automation. I have tested the automation twice and the exact same problem happens

Any ideas about why this is only sort of working?

Screenshot 2025-05-09 155403.png Screenshot 2025-05-09 155546.png

Accepted answers

Bill Sheboy

Hi @Sophia Skinner -- Welcome to the Atlassian Community!

Without seeing your complete rule (in a single image) and the audit log details, I have some questions which may help explain what you are seeing:

First, does the rule add each task, one by one, or is there any form of branching in the rule?
You describe "the first 7 tasks in the correct order, but will not complete the remaining 4". What do you mean by "will not complete the remaining 4"?
Your description indicates 7 + 4 = 11 tasks, but the image of the Epic shows 12 child tasks. Were those created by the same rule?
With the number of tasks added, and apparently setting the dates with manual increments of the values, have you checked for any errors in the number values for each task?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Sophia Skinner -- Welcome to the Atlassian Community!

Without seeing your complete rule (in a single image) and the audit log details, I have some questions which may help explain what you are seeing:

First, does the rule add each task, one by one, or is there any form of branching in the rule?
You describe "the first 7 tasks in the correct order, but will not complete the remaining 4". What do you mean by "will not complete the remaining 4"?
Your description indicates 7 + 4 = 11 tasks, but the image of the Epic shows 12 child tasks. Were those created by the same rule?
With the number of tasks added, and apparently setting the dates with manual increments of the values, have you checked for any errors in the number values for each task?

Kind regards,
Bill

Sophia Skinner_ojvlrb

Hello Bill, thank you for following up!

1. no branching see photo below

2. Number was wrong in my intial text. there are 16 total tasks. the first 12 populate and the last 4 do not.

3. same as above

Screenshot 2025-05-09 164623.png

Bill Sheboy

Thank you for that information.

Is the symptom the last four tasks added have incorrect values for the Due Date and Start Date, or something else?

If the dates are incorrect, please show an example of the values used to set the Due Data and Start Date values. I want to see the expressions, so please post those as text in your response (rather than as a screen image).

And, have you reviewed the Create Work Item actions for those four to confirm their expressions are correct?

Sophia Skinner_ojvlrb

Thanks for the help @Bill Sheboy

The last four tickets are populated with the following information as part of their automation:

Summary: TRR MEETING

Due Date: {{triggerIssue.dueDate.minusBusinessDays(20}}

Start Date: {{triggerIssue.dueDate.minusBusinessDays(21)}}

Parent: Trigger work item

As an example from another ticket where the automation does work:

Summary: Stakeholder TRR Documentation Development

Due Date: {{triggerIssue.dueDate.minusBusinessDays(51)}}

Start Date: {{triggerIssue.dueDate.minusBusinessDays(56)}}

Parent: Trigger work item

Sophia Skinner_ojvlrb

It was the parenthesis!! Thank you so much for that catch. I accidentally duplicated that error for the last 4 tickets. They are now populated. Really appreciate your help.

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-cloud