Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. 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

XMLWordPrintable

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

      I would like this ability because our team was very new to greenhopper and accidentally started many sprints by accident with incorrect items in them. I am not so much worried about deleting them as I am just wanting to rename to say "Test Sprint 1" etc. This will help from a visual perspective to tell which are "real" sprints and which are not real sprints.

        1. Screen Shot 2017-05-09 at 1.27.34 PM.png
          263 kB
          Ashley Blackmore

          Form Name

            [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

            Jakub Lazinski (Inactive) added a comment -

            Hi all,

            Thank you for your feedback on this suggestion.

            Your insights have been invaluable in helping us understand the issue better and prioritize. I'm 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

            Jakub Lazinski (Inactive) added a comment - Hi all, Thank you for your feedback on this suggestion. Your insights have been invaluable in helping us understand the issue better and prioritize. I'm 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

            Ashley Blackmore added a comment - - edited

            I'm pasting this on behalf of a customer that was unable to log in:

            Here’s a reason to fix JSWSERVER-5744. I can’t get rid of it the empty sprint below, and there is always one in the recent history that makes the chart look bad.
            We need to be able to delete these things asap. It can happen in several ways, and we need the ability to fix it.

            Ashley Blackmore added a comment - - edited I'm pasting this on behalf of a customer that was unable to log in: Here’s a reason to fix JSWSERVER-5744 . I can’t get rid of it the empty sprint below, and there is always one in the recent history that makes the chart look bad. We need to be able to delete these things asap. It can happen in several ways, and we need the ability to fix it.

            Paul Fox added a comment -

            Renaming via the API does not work via the latest versions of the ondemand Jira. We misnamed a few sprints and would really like to fix them all to match our new naming convention.

            Paul Fox added a comment - Renaming via the API does not work via the latest versions of the ondemand Jira. We misnamed a few sprints and would really like to fix them all to match our new naming convention.

            Kyle Wiltshire added a comment -

            +1 - this would have been an easy fix on a local instance. if no API or feature can be developed, why can't support change via SQL? its a trivial change.

            Kyle Wiltshire added a comment - +1 - this would have been an easy fix on a local instance. if no API or feature can be developed, why can't support change via SQL? its a trivial change.

            Bogdan Bezuz Citireag added a comment -

            +1 or please provide an example of API usage to change this with the 'on demand' service

            Bogdan Bezuz Citireag added a comment - +1 or please provide an example of API usage to change this with the 'on demand' service

            Andrew Dunmore added a comment -

            I'm very interested in this feature and updating it problematically is not sufficient for all scrum masters.

            Andrew Dunmore added a comment - I'm very interested in this feature and updating it problematically is not sufficient for all scrum masters.

            boardtc added a comment - - edited

            As some folk have been describing on https://confluence.atlassian.com/display/GH/Editing+or+Renaming+a+Sprint, this is a realy necessary feature.

            Our release started with one team working early and now with others teams having joined we have a standard naming.

            If one goes into the burndown chart report and tries to select a sprint one sees "sprint 1" which means nothing when there are a lot of teams.

            Please add this ability, it's just a name and does not affect content!

            boardtc added a comment - - edited As some folk have been describing on https://confluence.atlassian.com/display/GH/Editing+or+Renaming+a+Sprint , this is a realy necessary feature. Our release started with one team working early and now with others teams having joined we have a standard naming. If one goes into the burndown chart report and tries to select a sprint one sees "sprint 1" which means nothing when there are a lot of teams. Please add this ability, it's just a name and does not affect content!

            Colton Weeks added a comment -

            Sorry can you give a little more info? How do we change information using the API?

            Colton Weeks added a comment - Sorry can you give a little more info? How do we change information using the API?

            JPRivard added a comment -

            A colleague of mine found a solution to this problem, as the issue seems to be present only when using the interface. If we change information using the API, my colleague was able to change the sprint's name.

            JPRivard added a comment - A colleague of mine found a solution to this problem, as the issue seems to be present only when using the interface. If we change information using the API, my colleague was able to change the sprint's name.

            Colton Weeks added a comment -

            +1 for this feature!

            Colton Weeks added a comment - +1 for this feature!

              Unassigned Unassigned
              9432c5abe2ff Jeffrey
              Votes:
              69 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: