Agree with Bernadette.  This is very nice to see. Thank you, Atlassian Jira team!

But can we reopen parallel sprint ? It shows that closed sprint can be opened only when currect active sprint is closed. 

Thank you everyone! Really pleased. And thank you for the detailed documentation. https://support.atlassian.com/jira-software-cloud/docs/reopen-a-sprint/

Hi everyone,

This is Mark from the Jira Software team. Great news – we have now released this feature! You can also watch our cloud blog for future updates.

Thank you again for your suggestion to enable the reopening of completed sprints in team-managed projects.

Best,
Mark

I accidentally completed a sprint on Jira mobile app; and was unable to re-open the sprint.

It's fun watching this thread just to see how Atlassian not using the software product they made.

It's incredibly confusing how the sprints work. Even if your tickets are in a "DONE" status, they will still be moved to the next sprint UNLESS the tickets are in the farthest swimlane to the right. So, if your ticket is in a "DONE" status, but it's not in the farthest swimline on the right on the board, the tickets will be moved to the next sprint automatically. 

Yes please. The UX is incredibly confusing in that I closed a sprint, and all my "Done" status tickets were still moved to the next sprint!!!  There needs to be a way to undo/correct that

+1

Can anyone tell me all the new changes in the Jira that happened for the past 2 weeks?

When i close a sprint any open status/ Sub tasks/ in-completed/ defined  alerts are not throwing up any errors.

Today , i thought all the user stories were accepted but a task was pending in the user story and subsequently it did not throw an alert and it was moved to the next sprint which reduced the team's velocity.

Definitely looking forward for this classic capability to be enable in nex-gen. 

Looking forward to this enhancement!

https://getsupport.atlassian.com/browse/JST-646207

8092a6ba4de3 it should be available in the few weeks! Thanks for your patience.

Eoin, this there any timeline associated with this feature, it was first identified over 1 year ago.

I've updated the title and description to reflect the remaining work here - let me know if any of you were waiting on anything else as part of this suggestion.
We're going to pick this up and do it as an interim enhancement. In the future, we hope to improve sprint management more broadly but we understand that there is an important short term need here that needs to be solved. Apologies for the delay.
Thanks
Eoin
Product Manager

How can i manage my sprint (mistake closed) if i can't reopen it ? Are you used Jira in Atlassian company ????????

I get the feeling this is going to be the "edit tweets" of JIRA. 

Does anyone know how the voting up/down works and when/how the vote count promotes the issue to a work item or priority?
This is a 2 year old issue/request with 354 upvotes. Does this have a chance for implementation? 

Haha, of course, I forgot that was one of the reasons I got annoyed

Hi @savvas, yes there is but unfortunately it's skewed due to an old sprint that was closed by mistake

Isn't there a velocity report you can use @paul

This is presenting a problem for us also as we can't truly track velocity due to an admin error on closing a sprint

please add this functionality to next-gen boards, its so sad one can't to this currently!

Its been raised from 2years still not worked. I need to reopen my sprint in next JIRA. Please help

I really need to reopen it too, please add it back, plz

shocking!

NooOOOOoooo!!

COME BACK EOIN!

For the record, it has been 100 weeks since this issue was raised. Still no fix

+1

As a customer I want to be able to delete closed sprints so that my reports are accurate.

Pretty huge oversight. And it's been open since 19/Oct/2018 COME ON @Atlassian 

+1

This is infuriating

+1

+1 Why can't this basic feature be implemented - renaming a past Sprint?

Is the Jira database schema THAT bad? How do you rename a past Sprint? 

JHC you can rename a .doxc file by clicking on the filename.

I stopped using Jira almost a year ago because it was clear that Atlassian's development team was a useless disaster, but I remain subscribed to this issue for the entertainment value of the occasional email of yet another person complaining that this important feature has been missing for literally years.

+1 I closed the sprint while a couple of task were yet to be reviewed for a team. I now have no way of reopening the sprint and those tasks have moved to the next sprint. I lost all metrics. Why is this feature still not implemented?

+1

I closed the sprint by mistake and now am forced to recreate another sprint and loose metrics.

Or Maybe explain what the thinking was in NOT including basic functionality of previous generation Projects, aka is this designed intentionally to not be included OR have you just not gotten around to it?

+1

+1 Why has this request since 2018 not been implemented yet?

+1. Brutally unforgiving to not have an undo button, and have this ticket open for two years

+1 

+1

+1

+1

+1

+1

This would really help me! Thanks.

+1

+1

+1

+1

Totally essentially feature. Once a sprint is closed it's impossible to add new issues that were delivered during the sprint but were mistakenly not added!!

With "Complete Sprint" easy for novices to click, this is needed to undo a 'blunder'. Please up-vote. 

I love the next gen projects EXCEPT for this. I completed my sprint prematurely, and it has caused so many horrible repercussions!!

@joe.amato - I concur!  I've been so frustrated with the lack of feedback from Atlassian on this issue (and a couple others) that I used the "Help us improve JIRA" feedback form in hopes of getting some eyes on this open issue.  I'm beginning to think there is a black hole of issues somewhere that no one internally is seeing!  

Encourage everyone on this thread to do the same and include the URL to this ticket.  Hopefully, someone will hear the screams!

Does @ivanteong (issue owner) still work for Atlassian?  Trying to figure out why there are no official responses on what is clearly a critical issue for many paying customers.

This was raised in Oct 2018. That's a long time to wait for what is an essential feature!

We need this feature

+1

I could not believe that you guys don't have this basic feature  2 years have passed already.

Hey guys where is the update? Come on guys, it is ridiculous. Our company pays so much money on Jira and you don't have this basic feature. It is a shame! 

Hi Any update on this issue?

Is there any update on this? This has been requested since 2018 and is a simple feature that should be available by now.

Are we enabling this feature which would benefit us in a long way ..... 

This is insane. How can such a basic function be missing? I hope you guys have a good reason for it.

It has been the "next" generation for years now. They should just rename "Next-gen" to "Lite".

@Paul Carver's comment above hit it on the head.  Human error is uncorrectable in the tool.  In particular, marking issues as 'Done' past the sprint closure date means that sprint is broken and there is no way to fix it.

Ivan, I do think it goes beyond reporting and requires changes to the record.  For example, making the 'Sprint' field in the issue changeable via dropdown to select a past/closed sprint would alleviate part of the problem.

In the meantime, I'm converting all of my projects back to classic.  Too many issues with nextgen, including this dealbreaker issue.

Guys, this ticket has been open since 2018. What is the status? This is really annoying for anyone using nextgen boards. 

HI @louis van Zly,

Thanks for the reply.

Hi Anderson,

As far as I know there is no easy way to do this. You'll have to export all your tickets to excel, setup a new classic project and import the tickets you exported. This can be a bit fiddly and time consuming but is possible. Retaining attachments and comments have proven an issue at times in the past when doing this so just check the imported items properly BEFORE you delete the old project  Good luck

Hi Guys,

There is any way to move my board from the next-gen to the old one? 

Thanks.

Hi Ivan,

Our first use case is that a sprint was created and completed with one naming convention and a better one was arrived at after the fact. We now have no way to update the old names to the new convention which makes reporting difficult.

This won't be our last use case - it's just one of many many probable human errors we're likely to encounter moving forward. We need a way to correct simple human mistakes so they don't end up detracting from the value of your tools.

For me it doesn't matter anymore because we quit using Jira. This broken functionality wasn't the only reason, but it was one of the reasons.

Comments on this item keeps piling in. Atlassian, could you please provide an indication of when we can expect some action on this issue / feature request?

I'm regretting my choice of choosing a NextGen project.  Our team really needs the ability to re-open a sprint. It's silly not to have it.

NextGen project tend to work well when everything is fine. It's the exceptions that kill it. What's not easy is switching running projects back to classic projects to solve these issues as a workaround. In essence, to shift a team or company to NextGen is a bit like a "waterfall" change, since you can't undo that step and then get caught with things like this.