Move due-date of multitple sub-tasks/stories 2w in the future

[andre]

Hello, 

We are using automation to generate epics -> stories -> sub-tasks. This is being used to create a list for an onboarding of a new product for our clients. Sometimes we have a delay and this causes an inconsistency in the due-dates. We need to postpone the due-dates of around 60% of the sub-tasks. I have tried to used bulk-edit, but there you can only change the due-date to a specific date, not 2weeks in the future. Any ideas how can we perform this action? 

Maybe few more details about our version, we are using Jira Data Center at the moment. As for the automation once, the user creates an epic with the special field selection, the automation will be triggered. We usually have the structure of an EPIC -> Stories (around 6) -> Sub-Task (each story has around 10-20 sub-tasks). 

Thank you for your help and wish you an amazing day! :) 

[Stephen_Lugton]

@andre to answer your question and provide you with a bit more certainty that it will move only the stories/sub-tasks within the epic, I've made a slight modification to the 2 automations I suggested.

This takes the form of adding a label 'Delayed' to each Story that is a child of the Epic when the Epic due date is changed, and yes to answer the second part of the change you would need to make the change to the due date on the Epic.

In the first automation the label is added to the child stories as well as updating the due date on the stories:

When setting the label in the automation you need select ADDREMOVE from the 3 dots to the right of the labels field:

For the second automation I've updated the IF condition to include looking for the label 'Delayed' (and removed the 'Delayed' label as part of the automation):

[Stephen_Lugton]

Hi @andre ,

I'm going to make the following assumption with this answer:

• The due date for the epic, related stories and sub-tasks is going to be the same

The difference between @Aaron Pavez _ServiceRocket_ 's answer and mine is that I'm going to suggest using 2 automations and trigger them from updating the due date on the epic.

The first automation is to set the due date on the stories based on changes to the due date on the epic, so if my assumption above is correct all you will have to do is update the due date on the epic to a new due date and it will filter down to the child stories.  

The second automation then looks for changes to stories and updates the due date for the sub-tasks:

It is important for the 2nd automation to make sure that the checkbox to allow the rule to be triggered by other automations is checked:

[Aaron Pavez _ServiceRocket_]

Hi @andre 

You can do it with automation. Set the trigger as manual or scheduled. Since you do this when something is delayed, create a manual trigger to test it. You trigger this from the Story.

When: Manual

Branch : For subtasks

The edit : Due date : smart value {{now.PlusWeeks(2)}}

Screenshots

Hope that helps!

[andre]

Thank you for you answer guys @Aaron Pavez _ServiceRocket_ @Stephen_Lugton 

I was wondering about few things:

1. How to find out the value of the delay? Because it can vary depending on the change of the due date. The 2 weeks are not always the case. If the user is chaning the due date on the epic level, can we somehow get the difference between the previous date and the new one? 

2. Shall the user change the due date on the epic or directly on the sub-task?

3. We have 2 structures we are operating with Epic->Story->Sub-Task and Epic->Sub-Task. I assume it will be easier to build to separate automations for those 2 correct? 

4. How about adding a custom field(mutationDueDate) that will store the previous value and at the end of automation will be updated with the newest value?

5. Since it is Data Center version I cannot get a direct access to changelog/history, is there a way to get to those 2 dates below? 

Thank you for you ideas here! :) 

Wish you a pleasant day! 

[andre]

Thank you guys  for your suggestions! What is the certainty, that it will move only the stories/sub-tasks within the epic? Second question, I assume in case we need to perform a due_date change this should be done on the level of the epic, correct? 

@Stephen_Lugton @Aaron Pavez _ServiceRocket_