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 Rule: date change for sequential issues

Andrea Kargodorian

Hi everyone,

I've read many different answers on here but am still unable to get this automation rule to work. There are sequential issues within an epic. They are all linked to the epic. When the due date of an issues changes but a certain amount of time (e.g. 5 days, I would like to automatically change the other sequential issues by the same amount of time.

I keep getting an error message in the audit log (The duedate must be of the format "yyyy-MM-dd" (duedate)). I have gone to System - Look and feel and changed date format but this hasn't helped.

What do I need to do to the date format and how do I fix it?

Automation Rule.JPG Error Message.JPG

Accepted answers

Trudy P Claspill

Hello @Andrea Kargodorian

Welcome to the community.

In cases like this I find it useful to use the Log Action component to check what values I'm getting. So, I created a rule to be triggered like yours on a change to the Due Date field. Then I used Log Actions to check the value before the change, after the change, and the value that you are trying to use to set the Due Date in other issues.

Screen Shot 2022-10-17 at 5.24.31 PM.png

In your rule, what you have written is attempt to set the Due Date field to the difference between the original and new values of the Due Date in the trigger issue. What you need to do is set the Due Date to the new date when that difference is applied.

I'm still working out how to do that myself.

All comments

Trudy P Claspill

Hello @Andrea Kargodorian

Welcome to the community.

Screen Shot 2022-10-17 at 5.24.31 PM.png

I'm still working out how to do that myself.

Trudy P Claspill

Got it!

I opted to save the days of the date difference as a variable, before the For component.

Screen Shot 2022-10-17 at 6.05.28 PM.png

Then in the For branch I use that variable to update the Due Date of the issue I want to change.

Screen Shot 2022-10-17 at 6.06.24 PM.png

This is the whole rule...

Screen Shot 2022-10-17 at 6.09.18 PM.png

You might want to add some extra checks to your rule to check if the date that was changed was originally blank, or if the date in the sibling issue that you want to change is blank. Those could cause problems with the .Diff and .plusDays functions.

Thanks to @Stefan Salzl 's response on this post for helping me figure it out.

Andrea Kargodorian

Thank you thank you thank you!! This worked perfectly!

Bill Sheboy

Hi @Andrea Kargodorian -- Welcome to the Atlassian Community!

With a rule of this type, which branches to any issues with the same parent epic using JQL...Have you confirmed that the date of the trigger issue is not also changing?

If it is, you may want to modify the branch to exclude the trigger issue from the results.

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud