Totals in NEW_WI_COUNT are not accurate
I'm using the NEW_WI_COUNT table in a BIRT report for RTC 2.0 to display new Defect work items that have been created each day.
The results in the WI_COUNT column are not accurate compared to the actual number of work items that were created. The New Work Items by Severity report, which also uses the NEW_WI_COUNT table, is also returning the same inaccurate counts. |
2 answers
Hi Steven,
Sorry for the delay. First question: is there any possibility that archived artifacts could be changing the numbers? Do you have work items that were created in categories, or associated with team areas, or owned/created by users who are now archived? That can throw off the numbers depending on whether you told the report to include archived things or not. Second, which numbers are bigger? The one from the work item query, or the one from NEW_WI_COUNT? james
|
|
We found two things that threw the numbers off. The first was work items that had been moved to a different project area. The second was work items created after 8PM.
If a work item was moved to a different project area, a work item query would only return work items still in the project area but NEW_WI_COUNT stores the original project area that the work item first belonged to. If a work item was created after 8PM it would be counted in the following day's count. This is due to the NEW_WI_COUNT using the DAY_ID field from the WORKITEM_CHANGES table instead of the TIME_ID for its own TIME_ID field. Depending on what day you are comparing, the query could return more items or the total for that day in NEW_WI_COUNT could be larger. |
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.