How do I reopen a sprint in a Greenhopper scrumboard (v5.10.1)

[Jim Randell]

We have closed a sprint but we want to reopen it. the last time this happened:

1. I created a new sprint
2. put a single "bogus" issue in the new sprint
3. opened the "edit screen" (where I display the Greenhopper Sprint Field) for the bogus issue
4. captured the value from the Greenhopper Sprint Field (its a serial number)
5. searched for all the issues in the closed sprint (based on the Greenhopper Sprint Field)
6. did a batch change on the returned issues, updating the Greenhopper Sprint Field from their current ID(the old sprint ID), to the ID of the new sprint
7. removed the bogus issue i added to the new sprint (whose purpose was to provide me with the new sprint ID)
8. I deleted the old sprint
9. renamed the new sprint to match the old one.
10. updated every filter which references the sprint ID
11. updated every workflow which references the sprint ID
12. updated every swimlane which references the sprint ID
13. hoped I did not miss anything.

So, can you simply reopen a sprint?

[Keith Brings · Accepted solution]

considering it's easy enough for someone to accidentally close a sprint or the wrong sprint this is a bit of a issue.

[Dobroslawa Wierzbicka]

The feature request is here: GHS-7804 - please vote and comment!

[V B]

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?

[James Rickards]

See https://jira.atlassian.com/browse/GHS-7804 for the feature request.

[Woody Arnold]

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.

[Renjith Pillai]

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?

[Guy Lepage]

+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.

[Mike Premo]

I was able to reopen the sprint by modifying the JIRA database. Added this note to GHS-7804.

[V B]

+1...this needs to get fixed!!!

[Jim Randell]

any word on this? is it fixed in a newer version? (I have not found the time to upgrade)

[Deleted user]

+1 for this