-
Suggestion
-
Resolution: Duplicate
-
None
-
1
-
8
-
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
- 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
- Select the issue and all it's children
- Select Bulk actions
- Bulk change 'Rank'
- Set the new rank for all selected issues in the hierarchy
- duplicates
-
JSWCLOUD-19869 Changes to Rank of an Epic don't change the Rank of their child Stories.
- Gathering Interest
- is cloned from
-
JSWSERVER-25083 Ability to change the rank of an issue resulting in all descendents of the issue to also be ranked
- Gathering Interest
- relates to
-
JPOSERVER-2493 Portfolio plan sorting based on hierarchy
- Closed
- Mentioned in
- mentioned in
-
Page Loading...