JIRA Software Server updates for this Suggestion are now tracked at https://jira.atlassian.com/browse/JSWSERVER-9220

Kind regards,
Martin
JIRA Software

@mjopson has a decision been made on this? (for JIRA Server)

Also completely unable to use the Cloud service for legal reasons here. 

+1 on the Cloud vs. Server comment.  We are unable to use Cloud for legal reasons.

I hope you are correct, I've been observing what appears to be an ever-increasing gap of functionality between the platforms.

@chadalanjackson I assume that what Martin really meant, is that it's hitting Cloud right now and will probably get to Server releases soon. Usually, cloud gets things a bit faster.

This feature is now available in JIRA Software Cloud.
For more details please see Deleting a sprint

Kind regards,
Martin
JIRA Software

I strongly recommend to implement a feature to delete old sprints. 

Hi,

The possibility to alter historical sprint data in JIRA Cloud would be very interesting. Deleting closed sprints, changing start and end dates, etc. Strongly in favor of having this. 

I found a solution to this that worked for me - not sure if it will work in all cases. I reopened the closed sprint sprint I wanted to delete, removed all the issues from it (edit issue, clear the sprint field). It suddenly disappeared and is no longer visible in any reporting or on the Backlog page.

Not sure if a perfect solution but fitted my needs.

marian.skalsky1088654841,
When I try to delete a sprint using the plugin, I simply get an "Error Occurred" message.
Please advise.

Thanks Marian, I'll give it a try!

Hi Daniel. The plugin now supports JIRA 7.
You can check it out here https://marketplace.atlassian.com/1213850
Marian

Hi Matt,
Sorry, but there is no possibility to implement this feature for JIRA Cloud yet, as JIRA Cloud doesn't expose the API that could be used to address this.
Marian

Hi Marian,

Is there any intention to make this available to JIRA Cloud users?

Thanks,
Matt

Hi Daniel. We're just testing the plugin for JIRA 7 and it should be available within 24 hrs

Unfortunately your plugin won't work for me since I use Jira Software version 7 and your plugin only supports version 6.4.

Hi guys,

There IS A NICE WORKING SOLUTION for this problem.

We've faced the same issue here at Hotovo, so we decided to implement a plugin to solve it. It SHOWS the CLOSED sprints in JIRA Agile and allows you to UPDATE and DELETE them.
You can find it here in Marketplace
https://marketplace.atlassian.com/1213850

Feel free to try it out and when you like it, support us and buy it

Cheers,
Marian Skalsky

Same issue, my only solution was to change the sprint field in every issue and rename the sprint, reopen the sprint that I want to delete and then rename it to a less important name (such as Spring test).

This feature should be avaiable since the JIRA admin wants to train in order to learn the JIRA Agile mechanics. Please mopve this issue on the next update

I get the same error as Szalai above when trying the curl/REST command with JIRA Software (Jira 7):

 > curl -u admin 'http://localhost:8080/rest/agile/1.0/sprint/1' -X DELETE -H 'Accept: application/json' -v
Enter host password for user 'admin':
*   Trying ...
* Connected to localhost port 8080 (#0)
* Server auth using Basic with user 'admin'
> DELETE /rest/agile/1.0/sprint/1 HTTP/1.1
> Authorization: Basic YWRtaW46QmVyTjV6NEg1d1VVMzZxUEtaNg==
> User-Agent: curl/7.40.0
> Host: localhost:8080
> Accept: application/json
> 
< HTTP/1.1 400 Bad Request
< Server: Apache-Coyote/1.1
< X-AREQUESTID: 951x7686x1
< X-ASEN: SEN-L7148165
< Set-Cookie: JSESSIONID=9DE287160328A962DDEDA60EDC381B5F; Path=/; HttpOnly
< X-Seraph-LoginReason: OK
< Set-Cookie: atlassian.xsrf.token=BDVN-SJIE-L1T4-S4II|01e74302410d4f913cac7fc03ca38f2d659e03f7|lin; Path=/
< X-ASESSIONID: 61loa6
< X-AUSERNAME: admin
< Cache-Control: no-cache, no-store, no-transform
< X-Content-Type-Options: nosniff
< Content-Type: application/json;charset=UTF-8
< Transfer-Encoding: chunked
< Date: Tue, 26 Jan 2016 20:51:58 GMT
< Connection: close
< 
* Closing connection 0
{"errorMessages":["Only future sprints can be deleted."],"errors":{}}

I have to say that I find it pretty ridiculous that since this issue was raised the situation has actually gotten worse. It used to be possible to accomplish this through the REST api and now even that is impossible. What was the point of making this an illegal operation even in the REST api when it's clearly a feature people want to use even more?

+1 this is a really important requirement for us

The ability of cancelling a sprint is part of Scrum, although it is supposed to happen only very scarcely.
It messes up average mesure of velocity if we cannot delete and cancel a sprint.

This is an essential feature.

i tried to model an already done sprint. which turned out to be hard (maybe impossible) after removing all tasks and closing it

i now can not re-open it and i can not delete it.
i also can not even rename it to mark it as garbage
now it blocks the meaningful name for that sprint

please fix this. thanks

I would like the resolution to agile 6.7.8

We created a sample sprint following a tutorial video. Now we wish to delete it. Please action this so a 'Delete Sprint' option is selectable from the GUI. Many thanks in advance.

Thanks for clarifying.
Kind regards,
Martin
JIRA Software

mjopson - exactly. I followed the suggestion I found in 'Current Status' above and that's where it lead me. I'm on Jira Software Cloud.

If we have a sprint we used for testing purposes, or was setup incorrectly with incorrect dates and or issues, it would be easier to be able to delete it and start with a new Sprint than re-open it and have it muddy your reports.

m.ochalek1970816626 - could you clarify why the inability to reopen a sprint means you wish to delete it? I can assume but would like to be sure.

Kind regards,
Martin
JIRA Software

I'm unable to reopen the sprint due to the following issue:

Reopening the sprint is not possible because there are no issues in this sprint.
1 issue is already completed in another sprint, and cannot be moved back.

jmcbee1740354793, could you please create a support ticket at https://support.atlassian.com
That way we can provide you with support specific to your circumstances and with higher security.

Regards,
Martin
JIRA Software

I too would like to be able to remove a sprint. In my case I somehow managed to create issues, create a new sprint, add issues to sprint, start sprint and have JIRA tell me that my issues were created after the sprint had started. I found it annoying that my burndown chart didnt have a guideline so I closed the sprint and disassociated my issues with the sprint. Now I have a dead sprint that says I cant re-open it because I dont have any issues associated with it.

As noted in the Current Status field above, we have recently released the ability to reopen a sprint to JIRA Software Cloud, it will be available for JIRA Software Server in a forthcoming release, which may be of use for some cases/workarounds related to sprint deletion.

Kind regards,
Martin
JIRA Software

Yes! This should be an Admin ability, without question.

For those who want to remove a sprint, you can always log a support request with Atlassian asking them to delete the sprint at the database level. They don't like to do it (you'll get a stern warning about deleting data directly out of the database and unintended effects, blah, blah) but if you insist and have the sprint numbers to provide to them they will do it. I've done this before and it worked just fine.

If enough people ask for this via a support request, Atlassian might finally give it more attention since it incurs cost to them every time a support request has to be handled. Just my two cents.

I vote for the ability to delete a sprint. I created a test sprint and now am stuck with it.

Thanks for your feedback and comments, the JIRA Software team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com

The related issue to be able to reopen sprints is now available in JIRA Software Cloud and will be available for JIRA Software Server in a forthcoming release.

Kind regards,
Martin
JIRA Software

Seriously no action since 2013? Was this addressed in JIRA 7? Rebranding is great, but how are features being addressed?

Hi People at Atlassian,

I completely agree with the previous comments. Not being able to delete a stale sprint interferes with my work and adds clutter. Please fix this as soon as you can.

Thanks!

Hi people at Atlassian,

Please give this issue priority it deserves. Our system is clogging up with old irrelevant Sprints.

Thanks

Matt is right. This has been open since 2013... kind of sad.

Guys - you need to take this issue more seriously.

We're considering becoming a paying customer for JIRA Agile, but it doesn't fill me with confidence when we aren't allowed to rectify our own mistakes, nor is there a single technical solution available (even through the back door) as a stop gap.

The whole purpose of us using JIRA Agile is to get more transparency for our management (and the team) with the progress / priorities of our project.

If it's full of trash / tests / experiments then that isn't going to help in that endeavour.

Thanks

i know how you feel Alvaro.

Just my two cents. So we are getting quite few messages from our users confused that this is not possible. And as usual with this kind of JIRA problems there is a ticket (this one) which is several years old with hundreds of votes and no solution. Why?

Cheers
PS: This and other similar cases are developing a case in favour of migrating out of JIRA.

Same thing for me - I'm getting error message now:

{"errorMessages":["Only future sprints can be deleted."],"errors":{}}

Workaround 1 is not working anymore.

Jira AGILE version 6.7.7

{{
szalailadislav$ curl -u 'admin:admin' 'http://localhost:2990/jira/rest/greenhopper/1.0/sprint/2' -X DELETE -H 'Accept: application/json' -v

• Hostname was NOT found in DNS cache
• Trying ::1...
• Connected to localhost (::1) port 2990 (#0)
• Server auth using Basic with user 'admin'
  > DELETE /jira/rest/greenhopper/1.0/sprint/2 HTTP/1.1
  > Authorization: Basic YWRtaW46YWRtaW4=
  > User-Agent: curl/7.37.1
  > Host: localhost:2990
  > Accept: application/json
  >
  < HTTP/1.1 400 Bad Request
• Server Apache-Coyote/1.1 is not blacklisted
  < Server: Apache-Coyote/1.1
  < X-AREQUESTID: 947x8801x1
  < Set-Cookie: JSESSIONID=; Path=/jira/; HttpOnly
  < X-Seraph-LoginReason: OK
  < Set-Cookie: atlassian.xsrf.token=; Path=/jira
  < X-ASESSIONID:
  < X-AUSERNAME: admin
  < Cache-Control: no-cache, no-store, no-transform
  < X-Content-Type-Options: nosniff
  < Content-Type: application/json;charset=UTF-8
  < Transfer-Encoding: chunked
  < Date: Wed, 29 Jul 2015 13:47:51 GMT
  < Connection: close
  <
• Closing connection 0
  {"errorMessages":["Only future sprints can be deleted."],"errors":{}}}}

I need this feature.

Workaround does the job, thanks a lot!

+1 Please implement this ASAP. My Agile boards are starting to get cluttered. I have projects which run for years, and this really detracts form the Agile concept!

I don't think we need to actually Delete the sprint in it's entirety, but you should be able to "Archive" the sprint or "Hide" it. And then have a button which says "Show Hidden Sprints" or "Show Archived Sprints".

Whats the new URL syntax for version 2 of the API
The below isn't valid;
https://jira.example.com/rest/api/2/sprint/5/SprintID
What should it look like now?

+1 Please implement this feature asap

Would love to see a delete sprint feature. We created several sprints during testing that I would love to get rid of.

Thanks for workaround. Finally we got this working!

Command line which deletes closed sprint via REST API:

curl -u 'user:password' 'https://jira.example.com/rest/greenhopper/1.0/sprint/SprintID' -X DELETE -H 'Accept: application/json'

You need to replace:

• user:password with real JIRA user name and password
• SprintID with real sprint ID - you can find it as described in following article: https://confluence.atlassian.com/display/AGILEKB/How+to+rename+a+closed+Sprint+in+JIRA+Agile

+1...please implement this very simple feature. If you have a Rest call for it then someone has clearly determined that it is a good idea.