We have closed a sprint but we want to reopen it. the last time this happened:
So, can you simply reopen a sprint?
considering it's easy enough for someone to accidentally close a sprint or the wrong sprint this is a bit of a issue.
The feature request is here: GHS-7804 - please vote and comment!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
https://jira.atlassian.com/browse/GHS-7804shows as a "minor" issue...this needs to be raised to "critical" IMO! Also, how does one vote on it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FYI - I did a modified version of the above. Didn't use the "dummy issue". Rather I created a quick filter on the planning board with the old sprint ID. I then dragged these into the new sprint and started it. Then I did a couple of bulk updates:
1. I updated all the issues that were completed in the old sprint to the new sprint: Logic: Sprint = Old and Sprint != New (bulk update to new Sprint ID)
2. The sprint list was showing duplicate names (because Old Sprint ID and New Sprint ID use the same name intentionally) so I also cleaned this up. Logic: Sprint ID = Old AND Sprint ID = New. I updated all of these to New Sprint ID. This also removes the history if issues were in prior sprints, but that's not really critical info.
3. Finally I confirmed that there were no issues assigned to the Old Sprint ID.
Reporting looks pretty good e.g. not seeing velocity for the old sprint and the Sprint report for the new sprint looks accurate e.g. its reporting earned points. The burndown is not "accurate". I think because I added the completed issues to the sprint after I started it. I'm not sure a way around this. I think you'd need to get the completed items to show up on the planning board and add them to the new sprint before you start it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No I guess, it's still the same. And I guess that does not appear in the GH roapmap as well. Mostly it's a conceptual issue why we should be talking about reopening sprints, when a Sprint itself a small iteration that has just a life of two weeks. And if an issue is not included in a sprint for a complete duration of two weeks and no one has noticed, probably, there is more to the way Sprints are being run, rather than the tool. Comments?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 - This should have been thought of before Atlassian built Sprints. Doesn't it make sense to think 2-3 steps ahead when building products? This is a bit ridiculous to reopen a Sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was able to reopen the sprint by modifying the JIRA database. Added this note to GHS-7804.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
any word on this? is it fixed in a newer version? (I have not found the time to upgrade)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.