It's all about the answers!

Ask a question

Burndown Chart is not working: Getting message "No data available"


Parveen Patel (77119) | asked Mar 30 '17, 2:52 a.m.
edited Mar 30 '17, 2:55 a.m.

Hi All,

We have customized scrum process template to match our work flow. We are using RTC 6.0.1 and Process sharing in RTC.

I tried to run Burn down reports on our development server, it's working correctly on that server. I tried to run burn down report on our QA server for the project area which Is created from same process template as per Dev server, but for all burn down reports getting message "No data available"

 We have configured all the planning attributes which is required to run burn down reports, as well as mapped workflow with OSLC groups.

Also I have run the DCC jobs on QA server. Though the reports are not working. Also disabled "supports data cashing" option in reports resources. But No luck !!!

Any help would be much appreciated.

Thanks in advance !!

 


Comments
Lily Wang commented Mar 30 '17, 8:57 p.m.

Could you see any data in the Burndown report parameters?

Is there any problem with other reports such as Burnup or Work Items related report?
" We have configured all the planning attributes which is required to run burn down reports, as well as mapped workflow with OSLC groups.", could you clarify the details you configured?


Parveen Patel commented Mar 31 '17, 4:06 a.m.

Hi Lily,

Yes we have selected all the values in Burndown report query parameters.

Also this problem is with other reports as well for e.g. BurnUp, Open Vs Closed work items.

Same reports are working on other server for project area created with same process template.

OSLC groups are mapped in work flow of each work items to get Kanban Task Board.


Lily Wang commented Apr 03 '17, 2:18 a.m.

As you said the same reports on another server work fine, I suspect the issue is related to DCC.
You may consider to run a full load of DCC, and check the logs if any resource inserted into the data warehouse.
If the issue still persists, I suggest you contact IBM Support.

Be the first one to answer this question!


Register or to post your answer.