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

Cannot move issue from one sprint to another

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • None
    • None

      I have two sprints created, sprint 1 and 2. Sprint 1 is active. In planning mode, I cannot move an issue from sprint 1 to 2. I need to first move it from 1 to the backlog and then to 2. It should be possible to just change the sprint version.

          Form Name

            [JSWSERVER-9186] Cannot move issue from one sprint to another

            set-jac-bot made changes -
            Link New: This issue details JSWSERVER-9655 [ JSWSERVER-9655 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2851890 ] New: JAC Bug Workflow v3 [ 2933086 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2541597 ] New: JAC Bug Workflow v2 [ 2851890 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548388 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2541597 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 908370 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548388 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 746444 ] New: JIRA Bug Workflow w Kanban v6 [ 908370 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 536159 ] New: GreenHopper Kanban Workflow 20141014 [ 746444 ]
            MichaelA (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            MichaelA (Inactive) added a comment -

            This functionality has been implemented since version 6.3+.

            MichaelA (Inactive) added a comment - This functionality has been implemented since version 6.3+.

            Gregory Demotchkine added a comment - - edited

            Me too. This is crazy.. I am first obligated to remove this issue from one sprint then add it to another. Only having a backglog of 200 issues when I remove it, it gets lost in the backlog, then I have to find it just to add it to the next sprint.

            In our workflow issues would be in constant transition, getting pushed to later sprints.
            This becomes especially unconfortable when using multiple sprints running in parallell (currently experimental feature)
            and when using sprints as iterations.

            This is a major UX bug and should be fixed quickly.

            Gregory Demotchkine added a comment - - edited Me too. This is crazy.. I am first obligated to remove this issue from one sprint then add it to another. Only having a backglog of 200 issues when I remove it, it gets lost in the backlog, then I have to find it just to add it to the next sprint. In our workflow issues would be in constant transition, getting pushed to later sprints. This becomes especially unconfortable when using multiple sprints running in parallell (currently experimental feature) and when using sprints as iterations. This is a major UX bug and should be fixed quickly.

              Unassigned Unassigned
              c62b8e93cdad Jeff Storey
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: