Backlog Priority number getting messed up - by Mrinal B

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 788319 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/21/2013 9:21:53 AM
Access Restriction Public


We are using Team Foundation Service ( for most of our development work. Our Backlog Priority number started showing large integer numbers (such as 62500, 12500, etc) this morning, instead of the small numbers (scale of 1 - 5) that we have been entering. It used to work correctly before.

It screws up our prioritization process. Please help!


Sign in to post a comment.
Posted by Microsoft on 5/23/2013 at 12:05 PM
Hey Mrinal B, this is actually by design.
With TFS 2012, the system takes control of the Backlog Priority field, and sets the values in such a way that keeps the list sorted (in the way you ordered it in the product backlog screen), but creates gaps between the numbers, so that when you reorder a backlog item, we need re-number as few items as possible.

If you manually set the backlog priority field yourself, we will respect it when displaying the backlog, but as soon as you reorder something from the backlog, we are going to try to create gaps between the numbers so that future reorders can update as few work items as possible.

I hope this makes sense.

Gregg Boer - TFS Product Group
Posted by Microsoft on 5/22/2013 at 10:13 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 5/22/2013 at 12:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(