Reports stopped working
Hello.
After migrating our beta 2a server to M5a reports stopped working. There are several issues I am seeing: (1) When I look at the Charts tab of an iteration plan (ruch client and web) I get the following two errors in a seperare dialog: Multiple report descriptors found for: Multiple report descriptors found for: projectAreaId: _LvYyQI5lEdydKY-kDjO0nQ, reportId: workitems.OpenWorkItemsByType Multiple report descriptors found for: Multiple report descriptors found for: projectAreaId: _LvYyQI5lEdydKY-kDjO0nQ, reportId: workitems.OpenWorkItemsByType (2) Most reports in my Report Adminstration view produce empty results. All paramter fields are completely empty. I cannot select anything. Selecting 'current' checkboxes also does not produce results (3) Some reports produce a "TextData (id=310): + DataSet "Data Set" is not defined" (e.g. Team Velocity) I tried to re-upload the report designs to the server as described in the FAQ, but I either get another descriptor error saying that the report already exisits or the newly uploaded report still shows empty results. I also deleted reports and tried to upload them again, which also gives me these descriptor errors. How would I get these reports back into my view? Also interesting is that I see reports for my team in the Report Administrator, but not in the Team Area editor's Artifacts view where Reports section is shown empty. When I look at the report's properties dialog of a report in the Report Admin view, though, it clearly lists that team area. The only reports that do seem to work are the Repository Metrics reports. (We do not use build or SCM.) Any help would be greatly appreciated. Thanks and best regards, Peter Haumer. |
4 answers
Peter,
For (1), starting M5, we decided to enforce unique report ids in a particular project area. It would seem, you have several reports in different team areas within the same project area that have the same report id. To fix this, make sure you expand all the team area nodes in the report admin view and delete any duplicate reports. The work item reports show as blank because we made schema changes for the work item data that we collect in the data warehouse. So the import (from Beta 2 to M5) will clear any data previously collected. The next time the snapshot runs, the data will be recreated. For (2), We already found out about the problem in the Team Velocity report and fixed it in M6. We will be very glad to send you a patched up Team Velocity report design file. But first let's make sure you get going with the other Work Item reports. |
|
Hello Rafik.
Thanks a lot. This really helped. I deleted all reports from all team areas and started over. After deploying the reports again the errors went away and the reports are running now. However, I am not sure that the data was recreated correctly. The chart in the iteration plans does not show that items were closed, although they were. For example, an iteration plan showing that 43 out of 53 work items were completed in the iteration still shows a graph with 53 open work items at the end. Before the migration these graphs were correct. Am I missing something? Checking the history trail of these work items it seems that everything is still there, i.e. the dates when the items were closed are there. The graph just does not reflect that. (The server is running for 2 days now.) One other remaining issue is that the Team Area editor does not show any shared reports in the artfact view anymore. Is this a known one? Thanks again and best regards, Peter. P.S.: If you could send me the velocity report that would help a lot. "rjaouani" <rjaouani@ca.ibm-dot-com.no-spam.invalid> wrote in message news:fs6egb$mi9$1@localhost.localdomain... Peter, |
|
Peter, a plan is associated with a particular milestone. If you retarget work items from milstone m1 to m2 and then close them, a plan that describes m1 would still show a chart that says the workitems were open during m1. Can you please check if you can reproduce the issue with the Open Work Items by Type report and by leaving the Interval parameter as blank and see if the chart is correct.
To have the reports show up in the TAN, you will need to right click on the corresponding report template in the report admin view and select "Add to My reports". You can then drag the report from the My Reports folder to the proper shared folder. I will see if we can automate all of the above in M6 with may be a new action that says: restore defaults: The action would delete all reports in a particular project area, then deploys the latest report templates and creates instances of those in the Tan. |
|
Thanks a lot for your replies.
By milestone you mean the "Planned for" date, correct? I reviewed quite a couple of work item's history and the "planned for" did not change and the items were clearly closed inside that iteration's timeframe. Also the chart looked correct before the migration to M5a. I will send you an email with the connection details for the repository in case you would to have a look yourself. Perhaps, I am just missing something here. Thanks again and best regards, Peter. "rjaouani" <rjaouani@ca.ibm-dot-com.no-spam.invalid> wrote in message news:fs8a90$fhc$1@localhost.localdomain... Peter, a plan is associated with a particular milestone. If you |
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.