TFS 2013 中的堆栈排名数字突然混乱 [英] Stack Rank numbers suddenly messed up in TFS 2013

问题描述

我不知道它是否与我最近执行的 TFS 2013 Udpate 2 有某种关系，但突然间我们手动设置的许多 Stack Rank 数字都搞砸了，并且随机值非常高.

I don't know if it is related in some way to TFS 2013 Udpate 2 that I performed recently but suddenly many Stack Rank numbers we set manually are messed up and got very high random value.

我刚刚开始在日常工作中使用 TFS，我想知道我的这种行为是错误还是被认为是正确的.在第二种情况下，是否有一个选项可以设置以避免这种自动编号?

I have just started using TFS in my daily work and I would like to know if I this behavior is a bug or is considered correct. In the second case is there an option to set in order to avoid this automatic numbering?

推荐答案

Ewald 在这篇文章中解释了所有内容 幕后:Backlog Priority 或 Stack Rank 字段

Ewald explains everything in this post Behind the scenes: the Backlog Priority or Stack Rank field

在我们发布更改后，我们收到了来自对变化感到困惑的客户.如果客户已经设置通过 Excel 将 Backlog Priority 字段设置为值 1..N，旧的稀疏化逻辑使范围值几乎完好无损(尤其是顶级项目).但是，使用更新 2，一旦您添加或对积压项目重新排序，稀疏化逻辑设置字段大数字的价值观引入大差距，并给你好的表现.这种变化是有意的，也是设计的.积压Priority 字段一直是一个系统字段，而我们的建议不要手动更新字段.你仍然可以使用Excel 使用值 1..N 快速设置积压的顺序，但要注意稀疏化会开始.虽然值不同，积压项目的顺序仍然是一样！

After we shipped the change, we have received multiple reports from customers who were confused with the change. If the customer had set the Backlog Priority field via Excel to values 1..N, the old sparsification logic kept the range values pretty much intact (especially the top items). With Update 2 however, once you add or reorder items on the backlog, the sparsification logic sets the field values to big numbers to introduce big gaps, and give you good performance. This change is intentionally, and by design. The Backlog Priority field was always intended to be a system field, and our recommendation is to not update field manually. You can still use Excel to quickly set the order of the backlog with the values 1..N, but be aware that the sparsification will kick in. And although the values are different, the order of the items on the backlog are still the same!

这篇关于TFS 2013 中的堆栈排名数字突然混乱的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！