-
Suggestion
-
Resolution: Unresolved
-
JIRA Server 6.3.15
JIRA Agile 6.7.11
-
8
-
20
-
In previous versions of JIRA Agile I was able to rename closed sprint with incorrect name/number via JIRA REST API according to this guide:
https://confluence.atlassian.com/display/JIRAKB/How+to+rename+a+closed+Sprint+in+JIRA+Software
With a recent version of JIRA Agile I'm getting "Cannot update closed sprint" error message.
I'd like to keep the ability to update closed sprint via REST API at least in case an urgent change is needed.
{
"name": "VPN_91",
"startDate": "26/Oct/15 6:47 PM",
"endDate": "05/Nov/15 6:47 PM"
}
{
"errorMessages": [
"Cannot update closed sprint"
],
"errors": {}
}
- is related to
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
[JSWCLOUD-12845] Unable to update closed sprint via REST API
We changed our Sprint naming convention.
Sure would be nice to have the ability to retroactively apply that convention to closed Sprints so that our external reports sort properly +1
Looking for a solution here as well. I've had a number of project managers that decided to use different schemes, I need to normalize the sprint names to they are clearer going forward and for archival purposes
Silviu J
added a comment - This is still not working for Jira Cloud. Do we have a timeline for this change?
Silviu J
added a comment - This is still not working for Jira Cloud. Do we have a timeline for this change? This issue has been solved for Jira Software (See JSWSERVER-12845)
Is there a timeline for solving it on Jira Cloud?
Ashish Patel
added a comment - Does anyone have any workaround for this? Its getting critical for my team too.
Ashish Patel
added a comment - Does anyone have any workaround for this? Its getting critical for my team too. Yeah, the only problem is that when you reopen the sprint, change the name and close it, it overwrites the "completeDate" what totally breaks all charts for that sprint. It's ridiculous
Matt Seal
added a comment - Barry,
I'm not sure on v6.3.14 but on 1000.319.1 you go to Reports from the left-hand menu, then select Sprint Report, then select the sprint you which to rename from the dropdown below the report picker. The reopen option will be on the right-hand side
Matt Seal
added a comment - Barry,
I'm not sure on v6.3.14 but on 1000.319.1 you go to Reports from the left-hand menu, then select Sprint Report, then select the sprint you which to rename from the dropdown below the report picker. The reopen option will be on the right-hand side 
Barry Pickering
added a comment - Hi Matt,
Can you advise how I can access the Sprint review feature? We use JIRA server v6.3.14.
Thanks
Barry
Barry Pickering
added a comment - Hi Matt,
Can you advise how I can access the Sprint review feature? We use JIRA server v6.3.14.
Thanks
Barry Matt Seal
added a comment - There is a way to rename closed sprints. Go to Sprint review and reopen the sprint. Then rename the sprint and complete the sprint. It does mess with with the Sprint statistics and status report a bit, but otherwise worked without a hitch.
Matt Seal
added a comment - There is a way to rename closed sprints. Go to Sprint review and reopen the sprint. Then rename the sprint and complete the sprint. It does mess with with the Sprint statistics and status report a bit, but otherwise worked without a hitch. Hi,
I'm using JIRA Could and I need to use this functionality.
When I can expect to have this fixed ? I have some urgency.
Regards,
João Cerdeira
My company is fairly new to Jira and we had two projects unknowingly use the same sprint name.
We now have a number of reports that have issues from the two sprints in each others reports due to having the same sprint name. As the sprints are closed and nobody noticed this at the time we're now stuck with projects that have reports that are broken and incorrect and we have absolutely no way to fix them.
I'm not aware of a workaround unfortunately.
Kind regards,
Martin
JIRA Software
Apologies for the inconvenience but the cause are changes in the API. The previous API was private and not supported and we are currently building out the new public API which does not yet include this functionality.
We have therefore updated this issue from Bug to Suggestion and the referenced document will be updated in due course.
Kind regards,
Martin
JIRA Software
I can confirm that this happens in JIRA Server 7.0.0, JIRA Agile 7.0.4 using the agile/1.0/sprint method.
I wonder what kind of data issues might have been caused by this previous functionality that caused it to be blocked in latter versions. If there aren't any technical issues and you're unwilling to give users an interface to do it from the app, (see
JSWCLOUD-17977and JSWSERVER-15872) at least give us a back door to do the things we want to do.