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

As a Jira Software user, I would like to be warned when moving issues which are in a sprint

XMLWordPrintable

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

      It would be great to be notified if the sprint field has a value before moving an issue.
      This causes a lot of confusion, since the consequences of moving an issue which already belongs to a sprint are not very intuitive for end-users:

      My recommendation would be to display a warning during the move operation (i.e. Move Issue: Update Fields screen) such as the one below, and also to allow users to edit that field before moving the issue:

      Warning

      One or more issues belong to a sprint. Moving these issues will affect the boards which include them prior to and after the move operation. For more details, please refer to the article Same sprint displayed across different scrum boards.

            [JSWSERVER-11992] As a Jira Software user, I would like to be warned when moving issues which are in a sprint

            Gregory Kremer added a comment -

            This behavior is not acceptable - moving issue to another board should never followed by the duplication of the Sprint on the new board. It's border-line stupid action. In some cases board admins tried to delete Sprints that came from another board, not realizing that they were deleting active sprints. That has got to stop. 

            Gregory Kremer added a comment - This behavior is not acceptable - moving issue to another board should never followed by the duplication of the Sprint on the new board. It's border-line stupid action. In some cases board admins tried to delete Sprints that came from another board, not realizing that they were deleting active sprints. That has got to stop. 

            Jan Stähle added a comment -

            We are moving data for a customer from a big project created years ago to smaller slices. Hence we created new buckets (projects) and move the existing issues into them. The Sprints, since tied to boards which are updated afterwards pointing to the new projects, shall be preserved. Hope there will be an option to do that. Deleting Sprint info should therefore be an option but definitely not the standard approach. 

            Proposal: When moving an option should come up to either preserve the Sprint OR delete it. We need both. 

            Jan Stähle added a comment - We are moving data for a customer from a big project created years ago to smaller slices. Hence we created new buckets (projects) and move the existing issues into them. The Sprints, since tied to boards which are updated afterwards pointing to the new projects, shall be preserved. Hope there will be an option to do that. Deleting Sprint info should therefore be an option but definitely not the standard approach.  Proposal: When moving an option should come up to either preserve the Sprint OR delete it. We need both. 

            Angie Rieger added a comment -

            Moving issues in a project sprint to another project without removing the sprint tie is causing a lot of confusion!  Our team deleted a sprint since this functionality does not make sense (they weren't expecting to see the sprint in their project, and so deleted it unknowingly messing up the other project as well since the sprint deletes completely out of the original project)

            Angie Rieger added a comment - Moving issues in a project sprint to another project without removing the sprint tie is causing a lot of confusion!  Our team deleted a sprint since this functionality does not make sense (they weren't expecting to see the sprint in their project, and so deleted it unknowingly messing up the other project as well since the sprint deletes completely out of the original project)

            Vera Nyajure added a comment -

            @kenneth hamilton did you get a response on how to decouple the issues?

            Vera Nyajure added a comment - @kenneth hamilton did you get a response on how to decouple the issues?

            Volodymyr added a comment -

            +1

            Volodymyr added a comment - +1

            Dorian Zlatan added a comment -

            This really needs to be fixed

            Dorian Zlatan added a comment - This really needs to be fixed

            marie.mogridge added a comment -

            This needs fixing - it causes real time consuming problems -

            I have just done this myself even with the knowledge of sprint carrying across projects and it has left me in a real pickle !!

            Any pop up or forced behaviour would be a massive improvement 

            marie.mogridge added a comment - This needs fixing - it causes real time consuming problems - I have just done this myself even with the knowledge of sprint carrying across projects and it has left me in a real pickle !! Any pop up or forced behaviour would be a massive improvement 

            Kirstin Slevin added a comment -

            I experienced this as well and it has been frustrating 

            Kirstin Slevin added a comment - I experienced this as well and it has been frustrating 

            Kenneth Hamilton added a comment -

            +1 

            Once issues are moved, is there any way to decouple them? Will bulk clearing the sprint field be enough?

            Kenneth Hamilton added a comment - +1  Once issues are moved, is there any way to decouple them? Will bulk clearing the sprint field be enough?

            Natalia added a comment -

            +++

            Natalia added a comment - +++

              Unassigned Unassigned
              dconrad Danilo Conrad
              Votes:
              235 Vote for this issue
              Watchers:
              111 Start watching this issue

                Created:
                Updated: