I created a new work item called "Issue" and customized some of the fields. What I want to be able to do is create a report that will give me information on the new work item. I can run the "work item list" report, but I would like for it to give me information on some of the new fields I added. My question is how can I edit the report or create a custom report
I've opened the report site and opened the 'work item list' report, but I don't see a way to add new fields I've also opened report builder, but the source of data field comes up empty.
Could someone please guide me in the right direction
thanks,
aaron

New report
kanand
How do I install the "SQL Server 2005 IDW14 workstation components"
I had previously installed the SQL Server Express Edition... I went to install the SQL Server 2005 April CTP edition and choose workstation components only, however it stated I had already installed everything. However, when I go to Excel, it does NOT show the "Microsoft OLE DB Provider for Analysis Services 9.0" it only shows version 8.0.
Thanks,
~slee
___AUTUMNS_ENDING___
I've the same problems with report builder. Did you solve the trouble since that time. If yes, please let me know.
Thanks
Stephan
lennon60000
BoGeorge
Thanks,
Scott
jdeguenther
Aaron, sorry I overlooked this post for so long. The first thing you need to do is make sure the data from your work item type is being captured in the warehouse. In order to do this, just set the reportable setting on each field in your work item type. Use reportable="measure" for numeric values that you want to aggregate (like work, cost, etc). Use reportable="dimension" for attributes that you'll use to slice the data (priority, approval, etc). As an example, here are some fields from the MSF Agile Task work item type.
<FIELD name="Exit Criteria" refname="Microsoft.VSTS.Common.ExitCriteria" type="String" reportable="dimension">
<HELPTEXT>Flag to determine if this scenario should be tracked as an exit criteria for the iteration</HELPTEXT>
<REQUIRED />
<ALLOWEDVALUES expanditems="true">
<LISTITEM value="Yes" />
<LISTITEM value="No" />
</ALLOWEDVALUES>
<DEFAULT from="value" value="No" />
</FIELD>
<FIELD name="Rank" refname="Microsoft.VSTS.Common.Rank" type="Integer" reportable="dimension">
<HELPTEXT>Stack rank to prioritize work</HELPTEXT>
</FIELD>
<FIELD name="Discipline" refname="Microsoft.VSTS.Common.Discipline" type="String" reportable="dimension">
<HELPTEXT>The discipline to which the task belongs</HELPTEXT>
<ALLOWEDVALUES expanditems="true">
<LISTITEM value="Development" />
<LISTITEM value="Test" />
<LISTITEM value="Program Management" />
<LISTITEM value="Business Analyst" />
</ALLOWEDVALUES>
</FIELD>
<FIELD name="Remaining Work" refname="Microsoft.VSTS.Scheduling.RemainingWork" type="Double" reportable="measure" formula="sum">
<HELPTEXT>An estimate of the number of hours remaining to complete the task</HELPTEXT>
</FIELD>
<FIELD name="Baseline Work" refname="Microsoft.VSTS.Scheduling.BaselineWork" type="Double" reportable="measure" formula="sum">
<HELPTEXT>The number of hours of work from the baseline plan</HELPTEXT>
</FIELD>
If you've already deployed your project, you can add these settings to an existing work item type and import it with witimport.exe. The new fields will be picked up on the next warehouse run.
Having done that, you're ready to start building reports that use your work item type. Consider whether you want to use Excel or Reporting Services to build the report.
Excel
At this point, you have an empty pivot table bound to the WorkItem_Fact cube. There are a couple of important measures at the end of the Pivot Table field list: WICountAsOf and TransitionCount. You'll use WICountAsOf for most of the queries - it gives you the total counts for any slice. (This measure has severe problems when used to trend over time, so avoid that in beta 2). For example, if you want to do a Bugs by Priority report, use the WICountAsOf measure, filter to WorkItemType=Bug, and slice by Priority. TransitionCount is used to show the state transition activity. For example, if you want to see the number of bugs that were activated, resolved and closed over time, use TransitionCount. (This measure isn't calculated and doesn't have performance problems when used with the time dimension).
Reporting Services
To create a report using reporting services, you'll create a Report Project in Visual Studio. (You need Visual Studio 2005 Beta 2 and SQL Server 2005 IDW14 workstation components). Create a data source that points at the OLAP database, and then use the report wizard to create your report. Deploy the report to <server>/<project> and it will show up in the Team Explorer. Make sure the report filters on Team Project if you do this so that you're providing a project-specific report in the Team Explorer.
Andreas Sieber
I never received an answer to my question. This is still an issue, but I've been working some other problems. Currently I'm using the queries to give me the information I need.
I'll let you know if I find out any info. on the reports.
thanks,
aaron
Christian Kuendig
Can you please point out to some resources where I can find details on how to modify the team reports in VSTS and add new reports in VSTS.
I am seeking some elaborative information on the same.
This link does not have information updated still :-
http://lab.msdn.microsoft.com/searchbeta/default.aspx query=Team+reports&Filter=
and same holds for
http://msdn2.microsoft.com/library/ms181635(en-us,vs.80).aspx
Please do respond back..
Thanks in Advance.
IlanAvigdor
http://lab.msdn.microsoft.com/teamsystem/tfsreadme.aspx
StephenBarclay
However, the version 9.0 still does NOT appear in Excel.
Thanks,
Scott
AndrewKnight
And I really want to create my own reports with Team System...