Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90427

As a Project Manager in Jira, I want to be able to rename completed sprints

    • 2,947
    • 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.

      Atlassian status as of February 2024

      Hi all,

      This is Daniel from the Jira Software team. We’re excited to let you know that we quietly rolled this feature out last week to everyone except our Release Tracks customers; they will be able to use this in the April release.
      Check out the community article to learn more about this.

      Thank you,
      Daniel

      Project names may change after some time and other needs may demand users to change the sprints' names after they are marked as complete, so as a Project Manager in Jira, I want to be able to rename completed sprints.

            [JRACLOUD-90427] As a Project Manager in Jira, I want to be able to rename completed sprints

            please add

            Matt Kepple added a comment - please add

            Tim Roche added a comment -

            Another +1 for this feature! I have some closed sprints with dates in the name that are incorrect and it would be great to update these.

            Tim Roche added a comment - Another +1 for this feature! I have some closed sprints with dates in the name that are incorrect and it would be great to update these.

            PLEASE ADD THIS

            brett hanson added a comment - PLEASE ADD THIS

            FWIW, this has been open for a lot longer than 5 years. See JSWCLOUD-5744. Creating this issue, and then immediately closing JSWCLOUD-5744 as a duplicate was a really lame attempt to disguise how long this has been needed.

            Regardless, JSWSERVER-15872 is for Data Center, which is not EOL.

            Kent Rogers added a comment - FWIW, this has been open for a lot longer than 5 years. See JSWCLOUD-5744 . Creating this issue, and then immediately closing JSWCLOUD-5744 as a duplicate was a really lame attempt to disguise how long this has been needed. Regardless, JSWSERVER-15872 is for Data Center, which is not EOL.

            @Kent Rogers- Jira Server EOL is Feb 15, 2024.

            If Atlassian hasn't done it for Jira Cloud in 5 years since this request was opened, it's pretty unlikely they'll add it to Jira Server in the next... 9 days.

            Nick Orlando added a comment - @Kent Rogers- Jira Server EOL is Feb 15, 2024. If Atlassian hasn't done it for Jira Cloud in 5 years since this request was opened, it's pretty unlikely they'll add it to Jira Server in the next... 9 days.

            This should be linked to JSWSERVER-15872, which is the same issue but for Data Center. AND since this is being fixed, JSWSERVER-15872 should be fixed at the same time.

            Kent Rogers added a comment - This should be linked to JSWSERVER-15872 , which is the same issue but for Data Center. AND since this is being fixed, JSWSERVER-15872 should be fixed at the same time.

            Eoin added a comment -

            Hi all!
            We are working on this right now and we will provide clarity on a ship date in a few weeks!
            Thanks,
            Eoin
            Product Manager

            Eoin added a comment - Hi all! We are working on this right now and we will provide clarity on a ship date in a few weeks! Thanks, Eoin Product Manager

            We will really benefit from this feature - please add it to the next release 

            Clara Gavriliuc added a comment - We will really benefit from this feature - please add it to the next release 

            +1

            +1

            Shlomi Moses added a comment - +1

              eryan Eoin
              htemp Heitor T (Inactive)
              Votes:
              885 Vote for this issue
              Watchers:
              391 Start watching this issue

                Created:
                Updated:
                Resolved: