-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
Dear team,
As an Advanced Roadmaps Plan user, I would like to be able to automatically shift the start dates and end dates of all issues that are dependant on a particular issue, if the end that of that issue changes.
Example: There is a blocker bug that blocks start of several stories, and their dependants (testing, documentation, etc.). The expected end date of the bug fix has moved by several days, which means the stories won't be able to start on the expected start date, nor the issues dependent on them, and so one - dozens of work items need to have their dates shifted.
I would like to be able to auto-shift all the dates (both start end end) of all the issues based on the changes on end dates (or start dates, if using consecutive start of dependencies) - there could possibly be a confirmation step, e.g. "Would you like to shift all dependent issues accordingly, by X days?".
This requirement has come up repeatedly from many Plans users in our organization, since this is something they are able to do in MS Project easily. It was a blocker for some of them to switch to planning their projects in Jira from MS Project.
Thanks,
Daniel
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24937] Automatically shift dates of dependent issues based on blocker end date change
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
Hello,
Please vote also the cloud ticket: https://jira.atlassian.com/browse/JSWCLOUD-23211
Thank you!
@Iker Gutierrez Basoa as i mentioned before not sure why it wipes the start date but for my needs the fact that the due date moves and duration is kept works
Thanks Renato!
@ Cait Frizzell would you maybe have an idea how to solve this problem with the Start Date?
If I add this: issue.duedate.plusDays (fieldChange.from.toDate.diff(fieldChange.to.toDate).days)
to the Edit Start Date Field section, it actually updates the Start date of blocked issue, to be after its Due Date.
BR,
Gabi
@Gabriella Molnar-Tóth unfortunately i have the same issue but i preferer the that the duedate change and duration is kept, because if with the start date rules as you pointed out the duration changes.
I did create the rule suggested by @Michael Lanham on his comment on the 07Dec22 which technically changes both but again in some case it changes the duration of some tasks too
Thank you Renato, I'm very new to automation as well, but loving it! I must be missing something else then so will take another look.
Hi Renato,
I created the new rule as you suggested, but it keeps deleting the Start Date of the linked issue.
With my first try, I actually wanted to change the start date, as response to the change on the DueDate.
That is because I don't need the duration of the linked issue to be changed.
So when I postpone the DueDate with 5 days, I would like to postpone also the Start date of the linked issue with 5 days.
Would you mind helping me with the smart value for that?
Best Regards,
Gabi
@Milly Igwe definitely not an automation expert 
but I would say if the link types ( 'prerequisites' or 'dependencies' of) are properly set in Jira and can be selected when creating the automation can't see why it shouldn't work
Thank you for the below options. Is it possible to make this work for linked issues that are 'prerequisites' or 'dependencies' of?
I have tried to modify to that instead of 'blocked' but can't make it work.
Thank you 
I found some useful information on this feature in Jira
How to Effectively Work with Negotiated Dates in SLA Management