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