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

Ability to choose where new Issues will be added in the Backlog

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

      As per GHS-10472, as a JIRA Agile User I'd like to choose whether the issues I'm creating are added to the bottom or the top of the backlog, or if it should be added above the current selected issue.

      Some users may think a new issue should put it to the bottom of the backlog to prevent accidentally giving the issue a priority while others may prefer the current behavior, so giving the ability to chose which suits better for the users would be great.

      Current Behavior:

      • When 1 or more issues have been selected -> rank the new issue after the lowest ranked selected issue
      • When no issue is selected -> rank the issue at the top of where the plan mode is currently scrolled.
      • When not on plan mode, new issues are ranked to the bottom of the backlog

            [JSWCLOUD-10846] Ability to choose where new Issues will be added in the Backlog

            Proposal:

            Introduce a new, 2-step sorting option, where the main sorting is performed based on priority, and the the items inside of a priority are sorted by rank.

            Deleted Account (Inactive) added a comment - - edited Proposal: Introduce a new, 2-step sorting option, where the main sorting is performed based on priority, and the the items inside of a priority are sorted by rank.

            Paul Price added a comment -

            See also GHS-5368.

            Paul Price added a comment - See also GHS-5368 .

            Alternatively, being able to automatically set the Rank of an issue after Accepting (as a Post Function) would also do the trick, I think.

            Hans Wijnveen added a comment - Alternatively, being able to automatically set the Rank of an issue after Accepting (as a Post Function) would also do the trick, I think.

              Unassigned Unassigned
              mfernandes@atlassian.com Matheus Fernandes
              Votes:
              19 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: