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

Ability to change the rank of an issue resulting in all descendents of the issue to also be ranked

XMLWordPrintable

    • 1
    • 8

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

      Issue Summary

      When dragging and dropping a parent issue in the Portfolio 3.0 improved interface will only impact the rank for the issue you moved. The rank for all descendent issues will remain unchanged.

      This behaviour used to be the default behaviour in 2.0 but was changed due to feedback (more info: JPOSERVER-2493

      Allow the user to configure between the old ranking behaviour and the new ranking behaviour

      Steps to Reproduce

      1. Drag an epic (with children) from the bottom of the plan to the top

      Expected Results

      • The child issues of the epic would be ranked to the top when viewing story <-> story.
      • Auto-schedule would consider the child issues as high-priority.

      Actual Results

      • All child issues would also be ranked to the top - looking at only the story level issues, the child issues will remain ranked at the bottom
      • Auto-schedule considers these issues last.

      Workaround

      1. Select the issue and all it's children
      2. Select Bulk actions
      3. Bulk change 'Rank'
      4. Set the new rank for all selected issues in the hierarchy

              Unassigned Unassigned
              rchristian@atlassian.com Rhys Christian
              Votes:
              13 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: