Automatic resetting of Issue Due Dates for an assignee based on the progress made in a sprint

[Mohajit Acharya]

Let me write the problem statement by taking an example.

Let us assume User A has three stories to work on in a Sprint.

Story 1: Due Date - 23-Apr
Story 2: Due Date - 25-Apr
Story 3: Due Date - 27-Apr

Let me assume that Story 1 got actually completed early i.e. on 21-Apr which is 2 days earlier than the Due Date. In such a case the Due Date for the remaining Story 2 and Story 3 should be preponed by 2 days:

Story 2: New Due Date - 23-Apr
Story 3: New Due Date - 25-Apr

Subsequently, let us assume that Story 2 now got rescheduled to 25-Apr which is 2 days later than the last Due Date. In such a case the Due Date for the remaining Story 3 should be postponed by 2 days:

Story 3: New Due Date - 27-Apr

Can this be implemented by using Jira Automation rules? If yes can I get the corresponding Trigger - Condition - Action for this rule?

Thanks in advance!

[Ravi Sagar _Sparxsys_]

Hi @Mohajit Acharya 

I never did this but it might be possible to do something with couple automation rules.

Are you using due date as an end date? Since you are talking about Sprint, I believe the scope of the sprint is defined earlier. If Stories are finished on time or not on time then you will be able to look at the velocity chart to understand your team's velocity and then use that metric to improve estimation in future sprints?

What are you trying to achieve with this automation?

Ravi

[Mohajit Acharya]

Yes, I am using Due Date as the end date.

It is not about changing the scope of the sprint but dynamically rescheduling the work that has been taken up in a sprint in order to reflect the correct picture without much manual intervention. 

Velocity Chart for a sprint is available only at the end of the sprint but my requirement is during the ongoing sprint. I have traced a solution and in the process of analysing the same.

https://community.atlassian.com/t5/Jira-questions/Move-multiple-due-dates-automatically-for-issues-within-the-same/qaq-p/1873301

Thank you, Ravi!

[Bill Sheboy]

Hi @Mohajit Acharya 

Yes, and...to what Ravi suggests:

The other post you linked to is for a team using Kanban methods and not Scrum.  If your team is indeed using Scrum, perhaps consider how you are planning sprints and monitoring the progress of work toward the goals (e.g. with burn charts) rather than creating small-scale-planning due dates within the sprint.

However if those due dates could extend outside of sprint boundaries, please reconsider if Scrum is a good fit for your delivery or if other practices would help more.

Thanks, and kind regards,
Bill

[Mohajit Acharya]

Thanks for your valuable advice, @Bill Sheboy

No, we have not been having instances where Due Date is falling outside the ongoing sprint and we are a great fan of Burndown/up, Sprint Velocity, and Cumulative Flow chart. 

This Due date is meant primarily for those stakeholders who are not so much involved with the sprint and who prefer to see slippages in terms of overdue items during the course of a sprint.

We follow the discipline of having due dates for stories within a sprint of two weeks. And we want to keep a watch on these dates as we progress with the sprint.