Trigger all Issue and Child-Issue to have startdate and due date update to one year later.

[Brandon Monahan]

I have created an issue with child issues, that I am using as a template. I have set issues/tasks that reoccur at the same time each year.

I want to be able to CLONE my template, and then run an automation that automatically changes the date to one year later. By doing this I can keep my timelines intact, since the same deadlines occur at the same time each year. 

The best I have been able to do is change it 

{{now.plusDays(365)}}. Not what I want, but at least gets me closer to the year, but it won't let me alter the start date, which messes up the timeline.   I would prefer if it found the issues current date and then added 365 days to that. 

Has anyone figured out how to clone, then move all the dates forward a year to keep the timelines intact?

Any help is appreciated. 

Thank you. 

[Trudy Claspill · Accepted solution]

Hello @Brandon Monahan 

Welcome to the Atlassian community.

Can you show us screen images that show your entire rule, and that show the details of each step in the rule?

When you say "it won't let you" change the start date, exactly what do you mean? Are you getting an error message in the rule execution audit log? Or is the field simply not updating in the manner you expect? Please show use the rule execution audit log details for such a case, and show us one of the issues included in that execution of the rule.

[Brandon Monahan]

Thank you. 

I managed to get Start Date to Work. 



It now works to change the Start Date and the End Date to one year after the automation is run. 

However, what I really need it to do it Take the same start date and same end date from each issue and child issue, and just move it up by one year. 

Is that possible? 

[Trudy Claspill]

Hello @Brandon Monahan 

Yes, it is possible.

Can you show us screen images that show the details of the Edit Issues steps in the rule?

[Brandon Monahan]

Thanks. 

I am using the {{now.plusDays(365)}} for lack of ability to figure out how to point it at the current date it has on each issue and child issue and then add 1 year to that date for Start Date and Due Date. 

[Trudy Claspill]

For the Due date field try this:

{{issue.Due date.plusYears(1)}}

And for Start date try this:

{{issue.Start date.plusYears(1)}}

You can reference current data in the issue currently in focus in the rule using the {{issue}} object. Follow that with the field name, which is case and spacing sensitive. For more information refer to:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

For manipulating dates specifically, refer to 

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

There you can find that the plus function accepts several time units, including Years.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-plus-unit---

[Brandon Monahan]

Thank you. The 365 worked, but switching it to plusyears1 will be easier. 

With {{issue}} object I am not finding object on the page you linked. 

Would I have to link each issue, or can I link to the issue and the child issues? 

[Trudy Claspill]

With {{issue}} object I am not finding object on the page you linked. 

Can you expand on that? I provided multiple page links. Which one of those are you viewing, and what are you searching for?

Would I have to link each issue, or can I link to the issue and the child issues? 

I'm not clear what you are asking with that question.

By changing the Edit Actions as I've  recommended, each issue's Start date and Due date values will be advanced 1 year relative to its current value, with no concern for values in the other issues.

[Brandon Monahan]

Sorry. I did not fully understand. I have now implemented you process, and it moves all of my items start date / due dates to the next year, keeping my timeline flow intact. This will help greatly with my ability to move my templates from year to year. 

Thank you. 

[Trudy Claspill]

Great! I'm glad I could help you.

Please consider clicking on the Accept Answer button if my answer helped you solve your requirement. That will mark your Question as Solved, which helps others searching the forum find posts with validated solutions.

[Brandon Monahan]

Thank you. 

[Luka Hummel - codefortynine]

Hello @Brandon Monahan and welcome to the community!

You might find our app Deep Clone for Jira quite useful in this context. With it, you can clone entire issue hierarchies, including child issues, and use the Field Editor feature together with Jira expressions to set the new dates.