Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-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

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature 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.

            [JSWCLOUD-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

            Hiero Vilas Boas added a comment -

            Any updates?

            Hiero Vilas Boas added a comment - Any updates?

            Juan added a comment -

            Buenas tardes, sería beneficioso poder cambiar el nombre delos Sprints. facilita las cosas a medida que se desarrolla el proyecto y este, obviamente cambia. Gracias.

            Juan added a comment - Buenas tardes, sería beneficioso poder cambiar el nombre delos Sprints. facilita las cosas a medida que se desarrolla el proyecto y este, obviamente cambia. Gracias.

            Eoin added a comment -

            Please add votes and comments to https://jira.atlassian.com/browse/JSWCLOUD-17977

            Eoin added a comment - Please add votes and comments to https://jira.atlassian.com/browse/JSWCLOUD-17977

            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.

              Unassigned Unassigned
              9432c5abe2ff Jeffrey
              Votes:
              106 Vote for this issue
              Watchers:
              63 Start watching this issue

                Created:
                Updated:
                Resolved: