• Hide
      Atlassian Status as of 7th Sep 2017

      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 (under REST API changes section).

      JIRA Software 7.5 is now available to download so you can start planning your upgrade straight away!
      Learn more in our release notes.

      Cheers,
      Jakub Lazinski
      Product Manager, JIRA Server

      Show
      Atlassian Status as of 7th Sep 2017 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 (under REST API changes section). JIRA Software 7.5 is now available to  download  so you can start planning your upgrade straight away! Learn more in our  release notes . Cheers, Jakub Lazinski Product Manager, JIRA Server
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

      Request
      {
          "name": "VPN_91",
          "startDate": "26/Oct/15 6:47 PM",
          "endDate": "05/Nov/15 6:47 PM"
      }
      
      
      Response
      {
        "errorMessages": [
          "Cannot update closed sprint"
        ],
        "errors": {}
      }
      

            [JSWSERVER-12845] Unable to update closed sprint via REST API

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3070298 ] New: JAC Suggestion Workflow 3 [ 3656700 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626867 ] New: JAC Suggestion Workflow [ 3070298 ]

            JC added a comment - - edited

            Agree that this would be really handy. Especially when your current project is a legacy one and you want to streamline everything or simplify things. Previous managers could've done a mess with sprint naming and it is really sad you can't just rename them...

            EDIT: just saw there's a ticket for Cloud version and that it is still open. Will follow that one then.

            JC added a comment - - edited Agree that this would be really handy. Especially when your current project is a legacy one and you want to streamline everything or simplify things. Previous managers could've done a mess with sprint naming and it is really sad you can't just rename them... EDIT: just saw there's a ticket for Cloud version and that it is still open. Will follow that one then.

            Bill Smith added a comment -

            +1 on Sergii's comment: this would be very useful in Jira Cloud

            Bill Smith added a comment - +1 on Sergii's comment: this would be very useful in Jira Cloud
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326530 ] New: Confluence Workflow - Public Facing v4 [ 2626867 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

            It's been two months since the last question, so I am hoping it is OK to ask again.
            Is this feature available in JIRA Cloud? If not, do you have any ETA? I am still getting the "Cannot update closed sprint" error.

            Thanks

            Sergii Bondarenko added a comment - It's been two months since the last question, so I am hoping it is OK to ask again. Is this feature available in JIRA Cloud? If not, do you have any ETA? I am still getting the "Cannot update closed sprint" error. Thanks
            Radek Janata made changes -
            Link New: This issue is related to JSWCLOUD-12845 [ JSWCLOUD-12845 ]

            Yeah, it's very frustrating in Cloud that you cannot rename a running/closed sprint.

            Iason Dimitrakopoulos added a comment - Yeah, it's very frustrating in Cloud that you cannot rename a running/closed sprint.
            Jakub Lazinski (Inactive) made changes -
            Fix Version/s New: 7.5.0 [ 74736 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Jakub Lazinski (Inactive) made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 319095 ]

              Unassigned Unassigned
              radek.janata Radek Janata
              Votes:
              19 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: