Prioritize moved features in the next release when shipping releases

What is the challenge?

• When a release is shipped, any incomplete features that move into the next release are automatically placed at the bottom of that next release.

• For teams managing large releases or PIs, this creates extra manual work because they must scroll through a long list and drag those features back to the top as the next priority.

• There is no way to preserve the relative priority of moved features or control where they land in the next release after the previous release is shipped.

What is the impact?

• Shipping a release creates unnecessary cleanup work in the next release.

• Teams lose time reordering features instead of focusing on planning and prioritization.

• This is especially difficult for customers using large PIs or releases with many features, where moved work can easily disappear to the bottom of the list and disrupt backlog management.

Describe your idea.

• When a release is shipped and incomplete features are moved to the next release, put them at the top or allow users to control where those features are inserted.