I am also seeking a solution for this. Having the end date of a sprint determined only by when the sprint was closed makes it impossible to preserve consistency in the reports for the reality of sprint periods if for any of many reasons the sprint is not closed on the actual date it ends.
However, the solution presented here does not work (for me at least). Clicking the sprint end date does nothing. Am I missing something?
LATER: My issue is different and is for Jira Cloud. Modifying the end date was no problem once I understood it better. The real problem is the sprint close date. If a sprint isn't closed on the exact right date...too bad. The Jira reports are off from what is desired. Permanently.
Would modifying the start time of an active sprint affect anything else? Sprint work was not started on the date eg jan 1st , but the Sprint was created and start date was set as jan 1st. Work only commenced in eg jan 7 . Can I caller the start date without it affecting anything else?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs