Why ETL Data Collection Jobs does not reflect latest parameter values (say iteration, timeline etc) when running Dashboard viewlet like Burn Down charts ? ?
Sandhya Prabhu (1●6●10)
| asked Jul 31 '13, 1:57 a.m.
edited Jul 31 '13, 4:23 a.m. by Francesco Chiossi (5.7k●1●11●19)
Why ETL Data Collection Jobs does not reflect latest parameter values (say iteration, timeline etc) when running Dashboard viewlet like Burn Down charts ?
For example when we add new iteration say Sprint 2 and when running dashboard viewlets we are not able to see this value Sprint 2 under iteration parameter even if you we try this after many days and data collection jobs are successful ?. Does this mean ETL jobs are not running properly ? I will really appreciate your help ! Regards |
One answer
Hello Sandhya,
you can check the status of the etl jobs here: ccm: https://server:port/ccm/admin#action=com.ibm.team.reportsManagement.etlStatus jts: https://server:port/ccm/admin#action=com.ibm.team.reportsManagement.etlStatus I noticed the following. I got the new iteration as parameter in for example a Burn Down chart on a Dashboard after I had at least one Workitem where "Planned for" was set to this new Iteration. Then run the etl jobs. Hope this helps, Elisabeth |
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.