每当我们开始新的迭代时，我都必须在燃尽报告（以及其他报告）中设置迭代参数的默认值。要获取值，我遵循此说明（http://salvoz.com/blog/2010/05/04/tfs-2010-default-iteration-and-area-for-burn-down-report/），其中包括使用连接到 tfs 数据层上的分析服务的 Sql Management Studio 获取值。由于项目数量不断增加，这变得越来越困难。
获取迭代 ID 的更好方法是从报告中获取它们，其唯一目的是列出迭代并显示其 ID。报告可以优选地安装在项目集合根（即DefaultCollection文件夹）中，并且列出该集合中的所有项目的所有迭代。
有人已经有这个了吗？
Whenever we start a new iteration I have to set the default value for the iteration parameter in the burndown report (and also other reports). To get the value I follow this instruction (http://salvoz.com/blog/2010/05/04/tfs-2010-default-iteration-and-area-for-burn-down-report/), which includes getting the value with Sql Management Studio connected to the Analysis Service on the tfs data tier. This is becoming increasingly difficult since the number of projects is increasing.
A nicer way to get iteration id's would to get them from a report, whose sole purpose would be to list iterations and show their id's. The report could preferably be installed in the project collection root, i.e. DefaultCollection -folder, and list all iterations for all projects in that collection.
Anyone already have this?
发布评论
评论（2）
我最终创建了一个报告，其中列出了 TFS 中的所有迭代，并显示了它们的 id 和一个字符串，可以将其直接粘贴到燃尽报告的 IterationParam 的默认值中。
该报告看起来像这样 http://i41.tinypic.com/2qm2bs4.png
-可以在 此处。我安装在报告服务根目录下的 TfsReports 文件夹中。
原始sql位于此处
I finally created a report that lists all iterations in TFS and shows their id and a string that can be pasted directly into the default value for IterationParam for the burn down report.
The report looks like this http://i41.tinypic.com/2qm2bs4.png
The rdl-file that can be installed into Reporting Services can be found here. I installed in in the TfsReports-folder that is in the root of Reporting services.
The original sql was found here
我认为最好的方法是 John Socha -Leialoha 描述了如何使用 MDX Studio 连接到 TFS 的 OLAP 多维数据集。您可以在此处下载 MDX Studio。
OLAP 立方体中的迭代节点">
I think the best way to do it is how John Socha-Leialoha described using MDX Studio connected up to the OLAP cube for TFS. Here's where you can download MDX Studio.
You essentially end up dragging & dropping the iteration node to the Query Editor so that it will show you the Iteration ID.