Hello Ben,
The sorting in the Plan is defined by the issue rank value which is in turn used by the scheduling algorithm to define the schedule of the issue.
The following Documents go into these concept a bit more:
But the main take away is the comment: "items that are ranked higher will be considered more important, and Portfolio will attempt to schedule them before lower ranked items." So it's by design to keep the issues in the defined rank order in the plan, as reordering the issues changes the weight of the item for the scheduling as covered in the Scheduling behavior , If you disable Ranking and alter the sort order you loose the functionality provided by Ranking in the scheduling algorithm, such as drag and drop and dynamic date calculations.
Regards,
Earl
This reveals the Portfolio's origins as a scheduling program. I want to have the ability to sort by something like WSJF initially, to set a roadmap for my Train across all teams, then sort by relative rank later, as we start work on the features. The current version of portfolio forces me to use a JIRA board to do the initial wsjf ranking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.