Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9220

Allow Deletion 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 delete closed sprints in JIRA Software 7.5!
      Now, together with an ability to delete opened sprints (that is already available in JIRA Software), and an ability to rename 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.

      As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps (read more here), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server.

      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 delete closed sprints in JIRA Software 7.5! Now, together with an ability to delete opened sprints (that is already available in JIRA Software), and an ability to rename 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. As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps ( read more here ), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server. 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 some cases it could be very helpful if we have the ability to remove (delete) undesired sprints, not only planned sprints.

          Form Name

            [JSWSERVER-9220] Allow Deletion 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. We're excited to announce that we are shipping the ability to delete closed sprints in JIRA Software 7.5!
            Now, together with an ability to delete opened sprints (that is already available in JIRA Software), and an ability to rename 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.

            As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps (read more here), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server.

            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. We're excited to announce that we are shipping the ability to delete closed sprints in JIRA Software 7.5! Now, together with an ability to delete opened sprints (that is already available in JIRA Software), and an ability to rename 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. As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps ( read more here ), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server. 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

            BrightShadow added a comment -

            People, this is really needed to make all clean. Why such simple case is not possible. I know, some reports etc. but remove them also during removing whole sprint...

            BrightShadow added a comment - People, this is really needed to make all clean. Why such simple case is not possible. I know, some reports etc. but remove them also during removing whole sprint...

            Margie Petrusek added a comment -

            We really need this as well. This causes very strange issues if we move a story from one project to another. If it has been in any sprints in the original project, that sprint will move to the new project.

            Margie Petrusek added a comment - We really need this as well. This causes very strange issues if we move a story from one project to another. If it has been in any sprints in the original project, that sprint will move to the new project.

            Luis Gois added a comment -

            8 months later and we're still waiting and badly needing this on JIRA Server.

            Luis Gois added a comment - 8 months later and we're still waiting and badly needing this on JIRA Server.

            duane.mattos718027409 added a comment -

            @mjopson has a decision been made on this? (for JIRA Server)

            duane.mattos718027409 added a comment - @mjopson has a decision been made on this? (for JIRA Server)

            Steven F Behnke added a comment -

            Also completely unable to use the Cloud service for legal reasons here. 

            Steven F Behnke added a comment - Also completely unable to use the Cloud service for legal reasons here. 

            Tim Lloyd added a comment -

            +1 on the Cloud vs. Server comment.  We are unable to use Cloud for legal reasons.

            Tim Lloyd added a comment - +1 on the Cloud vs. Server comment.  We are unable to use Cloud for legal reasons.

            ChadAlanJackson added a comment -

            I hope you are correct, I've been observing what appears to be an ever-increasing gap of functionality between the platforms.

            ChadAlanJackson added a comment - I hope you are correct, I've been observing what appears to be an ever-increasing gap of functionality between the platforms.

            Miłosz Kosobucki added a comment -

            @chadalanjackson I assume that what Martin really meant, is that it's hitting Cloud right now and will probably get to Server releases soon. Usually, cloud gets things a bit faster.

            Miłosz Kosobucki added a comment - @chadalanjackson I assume that what Martin really meant, is that it's hitting Cloud right now and will probably get to Server releases soon. Usually, cloud gets things a bit faster.

            ChadAlanJackson added a comment - - edited

            Martin,

            With all due respect... so what? We're not on JIRA Cloud nor do we plan on being on JIRA Cloud in the foreseeable future. This ISN'T an answer to the problem.  This doesn't help anyone on this thread.

            The frustration that is coming across here is that this isn't the only time we, your paying customers, are getting these kinds of answers.

            We can't go to cloud due to a myriad of reasons, mainly (in our case) because of the lack of support numerous add-ons for cloud.

            ChadAlanJackson added a comment - - edited Martin, With all due respect... so what? We're not on JIRA Cloud nor do we plan on being on JIRA Cloud in the foreseeable future. This ISN'T an answer to the problem.  This doesn't help anyone on this thread. The frustration that is coming across here is that this isn't the only time we, your paying customers, are getting these kinds of answers. We can't go to cloud due to a myriad of reasons, mainly (in our case) because of the lack of support numerous add-ons for cloud.

              Unassigned Unassigned
              llima LucasA
              Votes:
              568 Vote for this issue
              Watchers:
              266 Start watching this issue

                Created:
                Updated:
                Resolved: