TFS Reporting on Customized Work Items

Question

So I copied the bugrates.rdl report that's standard with TFS 2008, renamed it to issuerates.rdl and added it to my reporting project.  Our Work Items are customized so an Issue has the following states:

Proposed
Active
Development
Ready For Testing
Ready For Production
Closed

So in the IssueRates.rdl file (the one that was formerly bugrates.rdl) I:
1) edited the parameter "Resolved" and made it, "Ready For Testing.
2) edited the parameter "Active" and added "Active" and "Development"
3) edited the parameter "Fixed" and added "Ready For Production" and "Closed"
4) edited the parameter "Bug" and made it "Issue" - since that's what I want to report on.

All the other parameters are the same, again, except for, active, resolved, fixed and bug, and note, I didn't change the "name" of the parameter just the "default values"/"non-queried" items.

The problem is that the report, when executed, shows like this (copy/paste in a new window):
http://farm4.static.flickr.com/3507/4011811521_0cb5dacf3f_o.jpg

The rest of the report looks OK...

The "Ready For Testing" is all baseline, 0, (the green line)... But that's not accurate there are items set to "Ready For Testing" during the timeframe the report was run!

Answer 1

Hello,

Here are the steps to troubleshoot the data issue in report:

1. Use SQL profiler to monitor the queries to OLAP database
2. Run the report
3. Check the MDX queries and find the main query of work items
4. If the query text is correct, copy and run the query in SQL Management Studio and view its result
5. Check the correctness of the result

Please let me know the result so that I can give you further action plan.
 

Hongye Sun [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Answer 2

attempting to do that now!

Answer 3

keep getting this:
"Parser: The query contains the Active parameter, which is not declared.
Execution complete"

Answer 4

the data still comes back as NULL when viewing in business intelligence studio... sigh

Answer 5

the result is always this:
http://farm3.static.flickr.com/2451/4014490539_17276ab407_o.jpg

NULL CITY!

Answer 6

ok!  Got the report working! but there's still 1 problem.  The report, which is basically the BUG RATES reported but saved as a new report, ISSUE RATES needs to have multiple states classified as the ACTIVE parameter.

An Issue, for us, has these states:
Proposed
Active
Development
Ready For Testing
Ready For Production
Closed

But the "active" parameter needs to include, proposed, active, development, ready for testing, and ready for production.  Technically, those are all active Issues.

I know the work items out of the box have an ACTIVE state, but while we have that, we also have those named above, which, technically mean that the work item is "active."  make sense!?  help!

Answer 7

I saw that the issue is resolved at:
http://social.msdn.microsoft.com/Forums/en-US/tfsreporting/thread/7650f699-802b-4275-93b6-2ff471cc328a


Hongye Sun [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.