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

When a sprint is completed incomplete issues should return to the top of the backlog

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

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      Problem Definition

      As of JIRA Software 7.1, when completing a Sprint, a popup will appear allowing the Admin to choose a Destination for Incomplete Issues if there are Sprints Scheduled. By Default, the Backlog is Selected; in previous versions of JIRA Software (Agile), incomplete issues will be returned to the top of the backlog.

      Current behavior: If you complete a sprint and then return all incomplete issues to the backlog then they will return to the location in the backlog they were before the sprint started. This means if you dragged them from the bottom (if you just created them for example) then they'll return to the bottom.

      See related: Completing a sprint

      Suggested Solution

      Issues should always return to the top of the backlog, as they were just included in a sprint it should be assumed that they are a high priority and they should appear at the top of the backlog instead of their previous version.

      Workaround

      • Drag issues to the top of the backlog before adding them to your sprint.
      • Create a future sprint and move incomplete issue there before closing the current sprint.

        1. J64_backlog.png
          J64_backlog.png
          56 kB
        2. J71_backlog.png
          J71_backlog.png
          52 kB

            [JSWSERVER-13636] When a sprint is completed incomplete issues should return to the top of the backlog

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066045 ] New: JAC Suggestion Workflow 3 [ 3663309 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626273 ] New: JAC Suggestion Workflow [ 3066045 ]
            Kamil Kolonko made changes -
            Affects Version/s New: 7.1.0 [ 59897 ]
            Affects Version/s Original: 7.1.0 Server [ 61099 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323093 ] New: Confluence Workflow - Public Facing v4 [ 2626273 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2041289 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323093 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031179 ] New: JIRA PM Feature Request Workflow v2 [ 2041289 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 1393749 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031179 ]
            jonah (Inactive) made changes -
            Description Original: h3. Problem Definition
            As of [JIRA Software 7.1|https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+7.1.x+release+notes], when completing a Sprint, a popup will appear allowing the Admin to choose a Destination for Incomplete Issues if there are Sprints Scheduled. By Default, the Backlog is Selected; in previous versions of JIRA Software (Agile), incomplete issues will be returned to the top of the backlog.
             !J64_backlog.png|thumbnail!
            Current behavior: If you complete a sprint and then return all incomplete issues to the backlog then they will return to the location in the backlog they were before the sprint started. This means if you dragged them from the bottom (if you just created them for example) then they'll return to the bottom.
             !J71_backlog.png|thumbnail!

            See related: [Completing a sprint|https://confluence.atlassian.com/display/JIRASOFTWARESERVER071/Completing+a+sprint]

            h3. Suggested Solution

            Issues should always return to the top of the backlog, as they were just included in a sprint it should be assumed that they are a high priority and they should appear at the top of the backlog instead of their previous version.
             
            h3. Workaround
            * Drag issues to the top of the backlog before adding them to your sprint.
            * Create a future sprint and move incomplete issue there before closing the current sprint.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSWCLOUD-13636].
              {panel}

            h3. Problem Definition
            As of [JIRA Software 7.1|https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+7.1.x+release+notes], when completing a Sprint, a popup will appear allowing the Admin to choose a Destination for Incomplete Issues if there are Sprints Scheduled. By Default, the Backlog is Selected; in previous versions of JIRA Software (Agile), incomplete issues will be returned to the top of the backlog.
             !J64_backlog.png|thumbnail!
            Current behavior: If you complete a sprint and then return all incomplete issues to the backlog then they will return to the location in the backlog they were before the sprint started. This means if you dragged them from the bottom (if you just created them for example) then they'll return to the bottom.
             !J71_backlog.png|thumbnail!

            See related: [Completing a sprint|https://confluence.atlassian.com/display/JIRASOFTWARESERVER071/Completing+a+sprint]

            h3. Suggested Solution

            Issues should always return to the top of the backlog, as they were just included in a sprint it should be assumed that they are a high priority and they should appear at the top of the backlog instead of their previous version.
             
            h3. Workaround
            * Drag issues to the top of the backlog before adding them to your sprint.
            * Create a future sprint and move incomplete issue there before closing the current sprint.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-13636 [ JSWCLOUD-13636 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: pse-request New: affects-server pse-request

              Unassigned Unassigned
              mhunter Matthew Hunter
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: