Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-13636

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

    XMLWordPrintable

Details

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

    Description

      NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? 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.

      Attachments

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

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: