When changing the work order in my Sprint View, why does my Product Backlog get rearranged?

Question

When changing the work order in my Sprint View, why does my Product Backlog get rearranged?

Jill Lunsford 0

We use the Cloud version of Azure DevOps. I have researched the Sprint Backlog Order field and understand that it no longer shows as a field in the Process section, but that it is still supposed to work. I have tried every option that I can find to keep this from happening. Our Product Owners spend a lot of time prioritizing the backlog and as soon as we start planning the work in the Sprint, the Product backlog gets rearranged.

Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-05T13:52:39.4+00:00
Hi @Jill Lunsford ,

Thanks for reaching out to Microsoft Q&A.

This is actually working as designed when you drag and drop items in the Sprint backlog, you’re updating the same priority field the Product Backlog uses.

What’s happening under the covers?

In Scrum the “Sprint Backlog Order” is really the Backlog Priority field; in Agile or CMMI it’s the Stack Rank field.

Both your Product Backlog and your Sprint backlog read from that one field.

When you reorder cards in the Sprint backlog (or taskboard), you’re changing Backlog Priority/Stack Rank and your Product Backlog immediately reflects that new ranking.

How to avoid it

Assign work to a sprint without touching the priority field:

In your Product Backlog view, turn on the Planning Pane (three-dot menu =>Planning Pane) and drag stories into your sprint there. This assigns the iteration without re-ranking everything.

Or multi-select items in the backlog, right-click and choose “Move to Sprint” again, doesn’t change their priority.

If you need to reorder only within the sprint, consider:

Using a separate custom field to track sprint-only order (you’d have to customize your process).

Training the team to use the Planning Pane or bulk-assign instead of dragging on the Sprint backlog.

References

Reordering updates Backlog Priority / Stack Rank fields

Assign work from your backlog to a sprint (without reordering)

Bulk-move items into a sprint via multi-select
Jill Lunsford 0 Reputation points

2026-05-05T14:21:37.1733333+00:00

Thank you Pravallika,

I am the administrator and I understand how to customize the Process. Can you please give me some more information on "Using a separate custom field to track sprint-only order"
Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-05T16:29:49.72+00:00
Jill Lunsford, you can track a sprint-only order by adding your own custom field instead of relying on Backlog Priority/Stack Rank.

Here’s a high-level approach:

Create a custom “Sprint Order” field

Go to your project’s process (Organization Settings → Process → select your inherited process).

Add a new field (type Integer or Double) to the work item types you use in your Sprint backlog (e.g. User Story, Bug, Task). Name it something like “Sprint Backlog Order.”

Add the field to the work item form

In your inherited process, edit each work item type form and drag your new field onto the form so people can see and edit it.

Show the field on the Sprint backlog cards

In Azure Boards, open one of your team’s Sprint backlogs or board.

Click the gear icon (“Column options” or “Card settings”).

Under Fields, add your “Sprint Backlog Order” field so it appears right on the cards.

Populate and maintain the sprint order

When you pull items into a sprint, leave the built-in priority alone.

Instead, use your “Sprint Backlog Order” field to indicate sequence. You can:

Multi-select items in the web and “Edit” to assign sequential values.

Export the sprint items to Excel, fill in the order numbers, then publish back.

Optionally use a simple on-form rule or Power Automate flow to default the field when you assign an iteration.

Sort your Sprint backlog by the custom field

You can’t drag-and-drop on the Sprint backlog to reorder by a custom field, but you can:

Create a Query that filters items by the current sprint and sorts by “Sprint Backlog Order.”

Use that query as your working list during sprint planning.

That way, your Product Backlog’s ranking (Backlog Priority/Stack Rank) stays untouched, and the team still gets a clear, sprint-specific sequence.
Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-06T08:20:56.3+00:00

@Jill Lunsford , following up to see if you have checked the above provided information and if it was helpful. Please let me know if you have any questions.
Jill Lunsford 0 Reputation points

2026-05-06T13:10:21.98+00:00

Pravallika,

Thank you for putting together your suggestion regarding adding an extra field and using queries with export, arrange, and import steps. After review, we’ve determined that this approach introduces too many steps for our teams to execute on a bi‑weekly cadence.

To minimize impact and keep the process simple and sustainable, we will move all Committed items to the top of the Product Backlog and drag cards to the bottom of the Sprint once they are marked as Done.

Thank you for the thoughtful proposal and analysis.
Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-06T13:15:48.38+00:00

@Jill Lunsford Thanks for the update. Could you please confirm if we can proceed to post the answer and close the ticket? If you have any further questions, feel free to revert back.

Answer accepted by question author

1 additional answer

Your answer

Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-05T13:52:39.4+00:00

Hi @Jill Lunsford ,

Thanks for reaching out to Microsoft Q&A.

This is actually working as designed when you drag and drop items in the Sprint backlog, you’re updating the same priority field the Product Backlog uses.

What’s happening under the covers?

In Scrum the “Sprint Backlog Order” is really the Backlog Priority field; in Agile or CMMI it’s the Stack Rank field.

Both your Product Backlog and your Sprint backlog read from that one field.

When you reorder cards in the Sprint backlog (or taskboard), you’re changing Backlog Priority/Stack Rank and your Product Backlog immediately reflects that new ranking.

How to avoid it

Assign work to a sprint without touching the priority field:

In your Product Backlog view, turn on the Planning Pane (three-dot menu =>Planning Pane) and drag stories into your sprint there. This assigns the iteration without re-ranking everything.

Or multi-select items in the backlog, right-click and choose “Move to Sprint” again, doesn’t change their priority.

If you need to reorder only within the sprint, consider:

Using a separate custom field to track sprint-only order (you’d have to customize your process).

Training the team to use the Planning Pane or bulk-assign instead of dragging on the Sprint backlog.

References

Reordering updates Backlog Priority / Stack Rank fields

Assign work from your backlog to a sprint (without reordering)

Bulk-move items into a sprint via multi-select
Jill Lunsford 0 Reputation points

2026-05-05T14:21:37.1733333+00:00

Thank you Pravallika,

I am the administrator and I understand how to customize the Process. Can you please give me some more information on "Using a separate custom field to track sprint-only order"
Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-05T16:29:49.72+00:00

Jill Lunsford, you can track a sprint-only order by adding your own custom field instead of relying on Backlog Priority/Stack Rank.

Here’s a high-level approach:

Create a custom “Sprint Order” field

Go to your project’s process (Organization Settings → Process → select your inherited process).

Add a new field (type Integer or Double) to the work item types you use in your Sprint backlog (e.g. User Story, Bug, Task). Name it something like “Sprint Backlog Order.”

Add the field to the work item form

In your inherited process, edit each work item type form and drag your new field onto the form so people can see and edit it.

Show the field on the Sprint backlog cards

In Azure Boards, open one of your team’s Sprint backlogs or board.

Click the gear icon (“Column options” or “Card settings”).

Under Fields, add your “Sprint Backlog Order” field so it appears right on the cards.

Populate and maintain the sprint order

When you pull items into a sprint, leave the built-in priority alone.

Instead, use your “Sprint Backlog Order” field to indicate sequence. You can:

Multi-select items in the web and “Edit” to assign sequential values.

Export the sprint items to Excel, fill in the order numbers, then publish back.

Optionally use a simple on-form rule or Power Automate flow to default the field when you assign an iteration.

Sort your Sprint backlog by the custom field

You can’t drag-and-drop on the Sprint backlog to reorder by a custom field, but you can:

Create a Query that filters items by the current sprint and sorts by “Sprint Backlog Order.”

Use that query as your working list during sprint planning.

That way, your Product Backlog’s ranking (Backlog Priority/Stack Rank) stays untouched, and the team still gets a clear, sprint-specific sequence.
Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-06T08:20:56.3+00:00

@Jill Lunsford , following up to see if you have checked the above provided information and if it was helpful. Please let me know if you have any questions.
Jill Lunsford 0 Reputation points

2026-05-06T13:10:21.98+00:00

Pravallika,

Thank you for putting together your suggestion regarding adding an extra field and using queries with export, arrange, and import steps. After review, we’ve determined that this approach introduces too many steps for our teams to execute on a bi‑weekly cadence.

To minimize impact and keep the process simple and sustainable, we will move all Committed items to the top of the Product Backlog and drag cards to the bottom of the Sprint once they are marked as Done.

Thank you for the thoughtful proposal and analysis.
Pravallika KV 14,395 Reputation points Microsoft External Staff Moderator

2026-05-06T13:15:48.38+00:00

@Jill Lunsford Thanks for the update. Could you please confirm if we can proceed to post the answer and close the ticket? If you have any further questions, feel free to revert back.

Answer 1

Hi @Jill Lunsford ,

Thanks for confirming your approach, this should help maintain clarity without adding operational complexity.

What you're seeing is expected behavior in Azure DevOps. When items are reordered in the Sprint backlog, the system updates the same underlying priority field used by the Product Backlog.

In Scrum, this is the Backlog Priority field, while in Agile or CMMI it’s referred to as Stack Rank. Since both views rely on this shared field, any reordering in the Sprint backlog is immediately reflected in the Product Backlog.

To avoid unintentionally changing priorities, you can assign work to a sprint without impacting the ranking by using the Planning Pane in the Product Backlog or by bulk moving items (“Move to Sprint”). If sprint-only ordering is needed, options include using a custom field or guiding the team to avoid drag-and-drop reordering in the Sprint view.

Solution:

To minimize impact and maintain a simple, sustainable process, keep all committed items at the top of the Product Backlog and drag cards to the bottom of the Sprint once they’re marked as Done. This avoids adding extra process overhead while still providing a clear working order throughout the sprint.

Hope this helps!

If the resolution was helpful, kindly take a moment to click on User's image and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Changing the work order in the Sprint backlog changes the same underlying rank field that drives the Product Backlog order, so both views are being reordered together.

Key points:

Single ordering field per backlog level
For a given backlog level (e.g., Stories / PBIs / Requirements), Azure Boards uses a single order field:
- Stack Rank for Basic, Agile, and CMMI processes
- Backlog Priority for Scrum This field determines the sequence of items on the product backlog page and is updated by a background process whenever items are dragged or moved in any view that shows that backlog level.
“The sequence of items on a product backlog page depends on where you add or drag the items. As you drag items, a background process updates either the Backlog Priority (Scrum) or Stack Rank (Agile, Basic, and CMMI) field. These fields determine the order in which backlog items appear on a backlog page.”
Sprint backlog uses the same leaf items and same rank
Sprint backlogs show the leaf node work items (e.g., the same user stories/PBIs that appear on the product backlog) for the selected iteration. When those items are reordered in the Sprint view, their Stack Rank/Backlog Priority is changed, which immediately affects their order on the Product Backlog.
No separate “Sprint-only” ordering
The older “Sprint Backlog Order” behavior is effectively replaced by the shared rank field. There is no separate, independent ordering field for the Sprint backlog versus the Product backlog at the same work item level. Any drag-and-drop reordering of those items in the Sprint backlog will change the product backlog priority.
How to minimize impact on Product Owners’ ordering Within the constraints above, the practical options are:
- Avoid reordering the same backlog-level items (e.g., Stories/PBIs) in the Sprint view; instead, use Tasks under those items to manage day‑to‑day sequencing within the sprint.
- Keep the Product Backlog ordering activity to the main backlog view and treat the Sprint backlog as a filtered view of that order, not a separate planning surface for re‑prioritizing the same items.

There is no configuration switch in the provided material to decouple Sprint backlog ordering from Product backlog ordering; both are driven by the same Stack Rank/Backlog Priority field for that backlog level.

References:

Share via

When changing the work order in my Sprint View, why does my Product Backlog get rearranged?

1 additional answer

Your answer