Report on Estimated vs Actual
Hi
I am using a Formal Template. I have few Tasks where I have updated the Estimate and Time Spent field. For e.g if for a Task work Item Estimate field is set to 6hrs and Time Spent is updated with 8hrs. I am not able to see the report in the RTC Dashboard by adding the widget Estimated vs Actual. Any idea on how to get this report? Regards V.Niranjan |
4 answers
Ralph is correct.
The user needs to associate a work item category with a team area.
Also, the user must run a data warehouse snapshot *after* updating the work item category and creating the necessary work item related data.
|
Hi All
I did associate category to team area but the graph is still blank. I tried with JKE Banking sample and gives the same result. I did run the data warehouse snapshot and then tried but still the report does not show up. Please let me know. Regards V.Niranjan |
Hi Niranjan
Could you please check and confirm if the Quality Management Datawarehouse jobs passed? Best Regards Rajat |
Hi Rajat
I just ran the Quality Management Datawarehouse and re-ran the report but I get the following message. No work items with estimates and time spent data were found. Please let me know. Regards V.Niranjan Comments
Rajat Singh
commented Jan 21 '13, 6:43 a.m.
Hi Niranjan
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Can you explain what you mean by not being able to see the report? Is the graph empty? Are you getting an error message?
If you run the report by going to Report > Shared Reports, does the report load correctly?
I'm not sure if the Estimated vs Actual report requires that the data collection jobs be run, but you may want to try running the jobs and then see if the report displays as you would expect.
Lauren, we chatted on ST.. The graph is empty. The reason probably being that there was no category associated to a team area, hence no work item associated to a team area. Parameters were not selectable etc. It is not solved completely yet, but looks as one of the situations that have discussed here several times already, where the process and data is not configured in a way that the widget would get input.