"Add these to an iteration backlog": you can use the iteration path of the work items. Best practice is to create an iteration called backlog.
"Grouped into Stories": In TFS 2010, the default traceablity is that on a User Story you define the Test Cases which validate the User Story. The Bugs are reported against the Test Cases.
"Estimating": You can use the Remaining work field for that
"Prioritsing": You can use the Stack Rank field
"Mark actual effort": Use the Completed work field
During iteration planning we may decide to allocate X amount of time to fix outstanding bugs, so we creat a bug fixing story for that iteration of X story points.
Bugs are chosen that we think should be fixed within the iteration, a task is created for each bug along with a time estimate and any high level technical details. Note the task is created as a child of the story and also related to the bug.
The key is that bug work items are not developed against directly, a related task is.
发布评论
评论（2）
我听到您问题中的一些部分：
“将这些添加到迭代积压中”：您可以使用工作项的迭代路径。最佳实践是创建一个称为积压的迭代。
“分组为故事”：在 TFS 2010 中，默认的可追溯性是在用户故事上定义验证用户故事的测试用例。 Bug 是针对测试用例报告的。
“估计”：您可以使用“剩余工作”字段
“确定优先级”：您可以使用“堆栈排名”字段
“标记实际工作量”：使用“已完成”工作字段
I hear some parts in your question:
"Add these to an iteration backlog": you can use the iteration path of the work items. Best practice is to create an iteration called backlog.
"Grouped into Stories": In TFS 2010, the default traceablity is that on a User Story you define the Test Cases which validate the User Story. The Bugs are reported against the Test Cases.
"Estimating": You can use the Remaining work field for that
"Prioritsing": You can use the Stack Rank field
"Mark actual effort": Use the Completed work field
我们一直在做的是：
关键是错误工作项不是直接针对相关任务开发的。
What we have been doing is:
The key is that bug work items are not developed against directly, a related task is.