-
Suggestion
-
Resolution: Won't Do
-
691
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Eoin
Product Manager, Jira Cloud
It would be helpful to be able to change the end date and completion date of a closed sprint.
- is duplicated by
-
- Closed
-
- Closed
- relates to
-
JRACLOUD-90714 Agile sprint complete date value not updated as expected using the REST API
-
- Long Term Backlog
-
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-90761] As a product owner, I want to be able to change the Start and End date of a closed sprint
I would like to cast my vote for this essential feature. I just can't believe this is still an issue in 2024.
This is an issue also related to Confluence calendars. We have sprints whose planned end date has been entered wrong and as they have now been closed, the planned end date cannot be changed. The Confluence calendar functionality that brings the sprints from a project to the calendar, uses the planned start and end dates and not the actual start and end dates, which makes sense as the calendar typically is used to look into the future, but now we for example have one sprint that has already been actually closed but as the planned end date was entered mistakenly to year 2025, it now shows in the calendar.
**ATTENTION** @mcook et al - Given the number of votes and comments, can this be reassigned and considered for intake? My offer from 2022 still stands - I'm willing to be a test volunteer or participate in other ways to make this happen.
This issue is even more pronounced with the new Calendar view. You can see the completion dates of all sprints in there and it's very obvious when they're wrong. There is an "Edit Sprint" option, but all you can change is the sprint name and goal. Wish they'd add an option for the dates there too.
The fact that the completion date is automatically set causes issues with advanced planning, where the following sprint will then overlap the closed sprint, and the number of story points displayed in the sprint includes those from both sprints. It is very confusing when viewing capacity on the current sprint.
the status was changed to 'Future Consideration' on 11/Aug/2021 8:37 AM, aren't we in future yet? Can I please request Atlassian to consider this soon as possible?
this is very problematic in reports , why don't you fix it ? for almost 6 years ??? is it so hard ? more than 400 voted for it
we also need it
Would LOVE to have this fixed up, especially for the Jira Plans view and to fix up mistakes made by others (not intended) Thanks
I would like to vote for this essential feature as well (and unfortunately it is not possible to vote for a "closed" ticket).
Actually, in my company we can't no longer use any project management reportinng feature because of this bug. I am wondering if we should rather drop Jira and switch to YouTrack for instance...