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.
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.
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events