-
Suggestion
-
Resolution: Fixed
-
JIRA Server 6.3.15
JIRA Agile 6.7.11
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
-
JSWSERVER-5744 As a Project Manager in JIRA I want to be able to rename completed sprints that were added by mistake, so that I can clear up any confusion when looking at historics of sprints
- Closed
-
JSWCLOUD-12845 Unable to update closed sprint via REST API
- Gathering Interest
- mentioned in
-
Page Failed to load
- relates to
-
SW-2610 Failed to load
[JSWSERVER-12845] Unable to update closed sprint via REST API
Workflow | Original: JAC Suggestion Workflow [ 3070298 ] | New: JAC Suggestion Workflow 3 [ 3656700 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2626867 ] | New: JAC Suggestion Workflow [ 3070298 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326530 ] | New: Confluence Workflow - Public Facing v4 [ 2626867 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Link | New: This issue is related to JSWCLOUD-12845 [ JSWCLOUD-12845 ] |
Fix Version/s | New: 7.5.0 [ 74736 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 319095 ] |
Current Status |
New:
{panel:title=Atlassian Status as of 7th Sep 2017|borderStyle=solid|borderColor=#cccccc|titleBGColor=#dddddd|bgColor=#ffffff}
Hi all, Thank you for your feedback on this suggestion. Your insights have been invaluable in helping us understand the issue better and prioritize. We're excited to announce that we are shipping the ability to rename closed sprints in JIRA Software 7.5! Now, together with an ability to delete opened and closed sprints (also released in JIRA Software 7.5), you will have a full flexibility in cleaning up your data and adjusting the historical data to your needs. These changes are also possible via the REST APIs. [Read more here|https://developer.atlassian.com/jiradev/latest-updates/preparing-for-jira-7-5] (under REST API changes section). JIRA Software 7.5 is now available to [download|https://atlassian.com/software/jira/download] so you can start planning your upgrade straight away! Learn more in our [release notes|https://confluence.atlassian.com/jirasoftware/jira-software-release-notes-776821069.html]. Cheers, Jakub Lazinski Product Manager, JIRA Server {panel} |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2043330 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326530 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031445 ] | New: JIRA PM Feature Request Workflow v2 [ 2043330 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1083329 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031445 ] |