新创建的 TFS 2010 迭代不可见
我已经在 TFS 2010 中创建了一个新的迭代，并且不想在新的故事和查询中使用它。
但是，迭代不会显示在新的故事窗口中，刷新VS，重新启动VS，切换到其他项目，没有任何帮助。
我是团队项目中的项目管理员，并使用我尝试使用它的同一用户创建了迭代。默认权限未更改。 在其他工作站上与具有足够权限的其他用户进行测试也没有帮助。
我可能做错了什么吗？
I've created a new iteration in TFS 2010 and wan't to use it in a new story and query.
However, the iteration won't show up in the new story window, refreshing VS, restarting VS, switching to other project, nothing helps.
I'm a project administrator in the team project, and created the iteration with the same user that i'm trying to use it with. Permissions are not changed from default.
Tested on other workstation with other user with sufficient permissions also doesn't help.
Could I be doing something wrong?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
确保“Team Foundation 后台作业代理”正在托管 TFS 实例的服务器上运行，并且它在服务帐户下运行。请参阅 http://msdn.microsoft.com/en-us/library/ms252450。 aspx 了解更多信息。
Make sure "Team Foundation Background Job Agent" is running on the server hosting your TFS instance and it is running under a service account. See http://msdn.microsoft.com/en-us/library/ms252450.aspx for more information.
有点晚了，但我们遇到了同样的问题。
我尝试重新启动“Team Foundation Backgroud Job Agent”，但没有任何效果。
但我找到了一个解决方案，尽管我不确定这是否是一个错误。
我们在这个项目中使用 Scrum 模板，我没有用任何常规项目模板检查过它，但我怀疑它是相同的。首先通过右键单击 TFS 项目并选择“团队项目设置”-> 添加所需的新迭代。 “区域和迭代......”。
在“迭代”选项卡上，我们现在有 2 个迭代（至少在我们的例子中），并且在这些迭代中包含多个冲刺。如果您只有一个迭代，则可以添加示例迭代
将新迭代向下移动后，其新位置位于现有迭代下方，我能够在团队查询中看到并选择新迭代。如果新的迭代已经位于另一个迭代之下，只需将新的迭代向上移动即可。
这可能是一个错误，或者 Scrum 模板的使用可能会干扰任何同步过程，但上述方法对我们有用。
A little bit late but we encountered the same problem.
I tried to restart the "Team Foundation Backgroud Job Agent", without any effect.
But I found a solution, although I am not sure if it is a bug or not.
We are using the Scrum Template for this project, and I have not checked this with any regular Project Template but I quess it is the same. First add the desired new iteration by right clicking on the TFS project and selecting the "Team Project Settings" -> "Areas and Iterations...".
On the Iteration Tab, we have now 2 iterations (at least in our case) with multiple sprints within these iterations. You can add a sample Iteration if you have only one Iteration
After moving the new Iteration downwards, so its new position is beneath the existing Iteration, I was able to see and select the new Iteration in my Team Query. If the new Iteration is already beneath another Iteration, simply move up the new Iteration
This may be a bug, or the use of the Scrum template might interfere with any sync process but the above method worked for us.
在我的情况下，这是由字母顺序问题引起的。在我的迭代设置中，我在迭代的底部添加了“2.11”，然后查看工作项，但看不到新的迭代。
事实证明，工作项模板按字母顺序排序，并且不遵守迭代设置。所以我的迭代总是在那里，它只是在“2.1”和“2.2”之间，而不是我期望看到它的地方。
In my situation this was caused by an alphabetization issue. In my Iteration Setup I added '2.11' at the bottom of the iterations and then looked in a Work Item and couldn't see the new iteration.
Turns out the work item template was sorting alphabetically and not obeying the Iteration setup. So my iteration was always there, it was just between '2.1' and '2.2' instead of where I expected to see it.