I have a client where they work in predefined sprint dates - Always Start on a Monday and end on the next Friday.
In some instances, the sprint will be started or ended earlier or later depending on public holidays, but still keeping the cadence.
When the sprint was ended earlier (Friday and not the Monday)
The next sprint was started a day later due to the public holiday (Tuesday and not the Monday)
In AR it shifted the dates of all sprints.
What it also did was to shift the start and dates of the Issues set above an Epic called Feature, in the hierarchy, to start and end mid-sprint.
We tried playing around by editing the current sprint's start and end date by setting the dates to the actual dates the sprints would start and end if we had no holidays, but it did not fix the issue.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events