Bug was created for those interested in enhancing this: JSWSERVER-15859

andrew.dunmore - Atlassian Support will assist with this and create an issue if there is a Bug, they will advise of this on your support request.

Kind regards,
Martin
JIRA Software

I was able to find a workaround. Bulk update a single story into the sprint --> reopen it. It was able to get me through the problem, but I would think this should become a defect / enhancement longer-term since we should probably be able to re-open and empty sprint that is closed.

ERROR:  Is there an issue out there to track this?  I entered a support ticket today.

This feature is now available for both JIRA Software Cloud and JIRA Software Server.
The server release version is 7.1.0, please see the server release notes for further details.

Kind regards,
Martin
JIRA Software

ekurt - it is already available in JIRA Software cloud and will be available in the next major release of JIRA Software server, I'll update this issue with the version and release date in due course.

Kind regards,
Martin
JIRA Software

ekurt - please see Reopening a sprint

Kind regards,
Martin
JIRA Software

Waiting for resolve asap.

mvdkleijn - it will be available in the next major release of JIRA Software server. I cannot give a date at present but as a guideline it should be the first quarter of 2016.

Kind regards,
Martin
JIRA Software

When will the re-open sprint feature be available for JIRA Software server?

That's cool ! At long last
Thanks @martin_jopson !

dross - thanks for adding the link above.

Additional documentation can be found in the JIRA Software Cloud space at https://confluence.atlassian.com/display/JIRASOFTWARECLOUD/Reopening+a+sprint

Kind regards,
Martin
JIRA Software

For those of you looking for documentation on how to reopen a sprint, it's mentioned in the following update from Oct 25-31 in the Cloud Documentation: https://confluence.atlassian.com/cloud/25-october-2015-to-31-october-2015-785619063.html (see the section at the top called "reopen sprints".

Basically, you navigate to the Sprint Report for the sprint you want to reopen, and there is a new link on the far right side of the sprint report header that says "Reopen Sprint". Click on that, you will be given a warning screen that lists the issues that will be part of the reopened sprint, and then click "Reopen" to confirm. It's as simple as that.

Hi Martin,

Can you point us in the direction of some docs that show how to use the feature?

I'm a JIRA Cloud customer but I can't see the option currently (it's probably just me not looking hard enough).

Thanks
Matt

yay, persistance pays. It took two years, the software even changed its name (JIRA cloud) but finally the functionality is there. Thanks guys!

This feature is now available in JIRA Software Cloud. It will be available for JIRA Software Server in a forthcoming release.

Kind regards,
Martin
JIRA Software

+1. I created a test sprint to verify some changes to workflow and board, and now the sprint is going to count against my velocity. So this isn't just for accidents.

I'll add my support for this feature. My scrum masters often misname or close sprints before they should be. Being able to reopen a sprint would be very helpful. Right now Jira is dictating process instead of being a useful tool.

Thanks,
Joel BC

only via database manipulation in current version...

From a support thread GHS-21083:

How difficult is to enable a function like this?

Is there any workaround?

The feature to re-open an accidentally closed sprint is MUST MUST.

If Atlassian is not planning to fix this in near future, please AT LEAST share a workaround or even a way to make changes at database-level on the backend to re-instate the sprint to running status.

Accidental closure on JIRA Agile cannot disrupt our release progress. Please do the needful at the earliest.

you would think this is an obvious feature. A lot of wasted time recovering if someone mistakenly clicks a button.

this feature is a must

I just had to run through the (most excellent) support team to handle this function. I am a bit disenchanted to see that the request to make this a user feature is almost 2.5 years old.

Atlassian is taking a big hit on its reputation.
2 years, an undo is still not yet even planned...

I don't understand why this isn't a feature, it just makes no sense.

Scenario; I had a story with sub-tasks, which we thought would be done in a single sprint. It wasn't. So we changed the story to an Epic, and the sub-tasks to issues so that they could be split across two sprints. I can now no longer add the completed tasks to the complete sprint and my JIRA current sprint and backlog now makes no sense whatsoever, with tasks in there which were completed in the previous sprint.

Users are having a big problem with not being able to re-open a spint. If there this will never be a feature in Jira, please let us know. People make silly mistakes and need to be able to "Undo" their mistakes in using Jira.

if an issue like this is unassigned how can we get it assigned?
i mean we have 532 votes for this functionality - surely this must mean it is a feature that we require???
Please do something about this Atlassian!!!!

Please please please!!!!! This is an actual issue with my company - sometimes we need to reopen the sprint and are hog-tied with the lack of this functionality!

Thanks in advance!

UPVOTE. I accidentally closed this off too early and now our sprint is all messed up. I can't believe this isn't fixed.

I will add to the comments here. I consider this a bug, at least a usability bug.

Votes: 509
Please escalate this request - the number of Votes certainly justifies it.

I am also highly disappointed from the fact that JIRA devs / business need 2+ years .. AND it is still NOT fixed ....

Wow! I didn't realize this has been around for 2 years already. Any plans to make the update? or should we wait for Slack to enter this market as well and take over the space?

herarg1, thanks for your comment.
JIRA Agile 6.6.70 and newer versions now separate the Complete Sprint and sprint editing functionality. Complete Sprint is available on Active Sprints (work mode) but the editing of a sprint name or dates is now done only in the Backlog (plan mode). This should address the concern you raise regarding accidental closure of the sprint due to these actions being in the same small dialog.
A screenshot and details of the newer Complete Sprint action can be seen at https://confluence.atlassian.com/display/AGILE/Ending+a+Sprint
Details for editing are at https://confluence.atlassian.com/display/AGILE/Editing+or+Reordering+a+Sprint#EditingorReorderingaSprint-Editingasprint

Kind regards,
Martin
JIRA Agile

I believe the option to "Allow reopen only for cases where: A subsequent sprint has not been started (and parallel sprints feature disabled)" would satisfy a large percentage of our needs as the need to re-open the sprint is usually immediately after "Accidental" closure.

Further, I also believe the accidental closure problem can be avoided or reduced significantly by making a simple usability/consistency design change(s) to the UI when changing sprint name or dates while in "Work Mode".
For instance, If user modifies either parameter, then:

1. Hide or disable the "Submit Sprint" button and replace with "Acknowledge Changes" button, or submit/cancel changes buttons.
2. Upon submitting/canceling modifications, replace with "Submit Sprint" button or just close the pop-up and default to "Submit Sprint" when re-opened.

The extra step only applies when user modifies original values; and will add an extra layer of protection against accidental closure due to natural human tendency.

Thanks for your additional feedback and comments, we understand this issue is important to many of you.

Previously we implemented GHS-6332 to help reduce the number of accidentally closed sprints. This name of the person who closed a sprint is now visible in the Sprint Report. This may help for cases that just need a social interaction.

We acknowledge that there is currently no simple workaround in the user interface, however this issue is tracked as a Suggestion since it is being tracked by the product team and not the bugfix team.

There is potential complexity around manipulation of the sprint and its issues once closed, for example:

• How do we deal with stories that were in a closed sprint, were incomplete and returned to the backlog, and are now in a new sprint (future or active)?
• What considerations must be made when parallel sprints are disabled and a subsequent sprint has been started.

Initially we would look to solve simple cases, as the main use-case is correcting the accidental closure of the sprint. A potential solution might be as follows.
Allow reopen only for cases where:

• A subsequent sprint has not been started (and parallel sprints feature disabled)

Reconstruct the sprint with the completed issues and only issues have not been assigned to another active sprint i.e. we would leave the issues in the active sprint.

• Issues that are in a future sprint would be taken back for the reopened sprint (essentially removes the future sprint's ID's).
• Additionally, we would not bring back issues that were removed from the sprint before its closure.
• Only ‘retrieve' issues from the backlog or future sprints. So if an incomplete issue from a reopened sprint was added to an active sprint (or future sprint that was started) we would leave it in that sprint.

If you have any feedback on this proposed solution please leave a comment below.

Kind regards,
Martin
JIRA Agile

From what I can see the grasshopper API allows the sprint name, start date and end date to be altered even when a sprint has been closed.

Do a PUT request to server/rest/greenhopper/1.0/sprint/sprintId/
with the following JSON data:

(replace server and sprintId with your own)

This solves some peoples problems on this issue regarding start date and name changes. Unfortunately due to a bug with how Jira uses the end date it doesn't resolve the issue for people who want to edit that. The end date will be updated but it is not the end date that is used for the reports. It is the completion date.

For more info see the below extract from the JSON representation of a sprint:
"startDate": "06/Jan/15 11:52 PM",
"endDate": "13/Jan/15 11:53 PM",
"completeDate": "06/Mar/15 1:10 AM",

Although the end date is set and can be modified using the above API call, the complete date can't be changed.
I'm not sure if the bug is that the reports use the completeDate as the endDate, that the completeDate can't be modified, or even that the endDate is named incorrectly but there is definitely a bug here.

@Martin It is also a question how much Atlassian is (really) listening to their users, and how is this perceived.
So Rainer's suggestion is valid from a user that feels being ignored!

Triggered by your comment I will check how our organisation and our JIRA users are feeling about this issue.
Kind Regards, Milan

@ Martin:

Thanks for your comment, Martin. We appreciate the contact regarding this issue. Would be interested to understand why this may be considered a suggestion vs. an issue/bug? If there are known workarounds, that would be spectacular to learn...

This is a very similar workflow to putting an issue into the "Closed" state. Atlassian developed a way to reopen bugs/issues/improvements after they've been closed because there is a major customer use case for this. We are only asking for the same functionality for Sprints as a whole. When something is closed it is possible that it will need to be reopened in the future for one reason or another. I know it probably messes up all of the post-sprint-closing-metric calculations, so it's a PM decision on that point.

Anyways, appreciate your note.

Martin Jopson,

While I do understand there are probably major features the team is working on, I still cannot agree it is acceptable for such a requires to have been logged for over an year and not have been addressed.

It does affect all Agile users a lot and placeholder answers are not helping prove anyone is acknowledging how big of a problem this is. Thus, people considering the option to contact the CEOs is only natural.

Best regards,
Nadia

rainer mueck, these issues are not being ignored by JIRA product management. An overview of how the JIRA team uses jira.atlassian.com can be found here: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

Using the Contact the CEOs form is not a recommended or preferred way to comment on a particular Suggestion or backlog item and will not change the priority of the backlog.

We understand this issue is important to many of you, we see it as a valid Suggestion, however we cannot provide any guidance at this time as to when we'll be implementing it.

Kind regards,
Martin
JIRA Agile

It seems to be the sad tradition, that the most voted GHS requests keep on being ignored by the JIRA Agile product management (see attached screenshot "JIRA Agile Most Voted.jpg") for a long time.

I keep on complaining about this fact whenever I meet Atlassian guys.

Everyone who feels frustrated like me, please go for it and use this method: https://www.atlassian.com/company/contact/contact-ceos

I did that twice already, but I bet it will make a difference, if dozens of us go that way.

As this issue is open now since two years : please tell us when this will be fixed!

One of our users has just accidentally closed a sprint. Having got over my disbelief that there's no way to undo this, I think this is a major flaw that needs to be addressed and will certainly make us think about whether we should continue with JIRA agile. Creating a new sprint and manually adding hundreds of issues to it again isn't a viable workaround for us.

I am interested very much for this feature.

I think we need both. Mistakes happen. We need an easy way to recover from them.

Ahh found a reason I would like to reopen a sprint. The name is incorrect and I would like to fix the name. If I could fix the name of a closed sprint without reopening the sprint ( and without going into the database) that would be fine too.

this is a must!

This really should be addressed, no way to fix a simple and common 'oops' really seems wrong.

For those interested in a UNOFFICIAL way to reopen your sprint, you can modify the JIRA database form associated with the sprint. Mine was called "ao_60db71_sprint.frm" and located in C:\ProgramData\MySQL\MySQL Server 5.5\data\jiradb. I've attached a couple screenshots, but I have successfully modified the start time of my sprint using this method. There is also a CLOSED field, which if you set to 0, it might do the trick.

Disclaimer: If not careful, be warned that you can mess your database and JIRA instance up this way. Backup first!

Cheers!

Has there been a fix for this yet?

I accidentally entered the wrong end date for a sprint and then closed it. Stupid mistake of course and there is no way to revert this It would be great if I can reopen the sprint.

folks, this is a MUST feature !!! im stuck with a closed sprint by accident !!!
need to have the re-open option !!!

This shouldn't be a "Suggestion" instead a bug in the current world.

Can someone from Atlassian confirm when they plan to implement this, it's such a nuisance that we can't reopen an accidentally closed Sprint either.

This is an important and needed feature. Any ideas when you will be able to work on this?

+1 Reopening Sprints is a MUST HAVE. Or you add an Undo funciton