It's all about the answers!

Ask a question

Why is the burndown snapshot not updating?


Norma Madrid (2515) | asked Jun 10 '15, 3:48 p.m.

ACTION: Create a burndown report with a specified iteration. Timestamp for data collection jobs shows that it stopped updating on the last day(AM) of the iteration's duration.
BACKGROUND: User is noticing that their burndown charts are not showing updates from a certain time-frame.
QUESTION: Do the data collection jobs stop collecting and updating data for iterations whose duration is over? 


Comments
Norma Madrid commented Jul 06 '16, 2:04 p.m.

UPDATE:
Our nightly ETL job failed and did not pick-up changes after the iteration had ended.

As a precaution, we have moved from ETL to DCC jobs to increase the frequency at which the data collection is updated. However, there is no way to correct the missing information from the burndown/burnup graphs.

A workaround that can be used if the missing information is discovered soon after the iteration is completed, is to extend the iteration end-date, so that the next ETL job can pick-up any closed tickets. This, of course, is not good agile practice.

Accepted answer


permanent link
Krzysztof Kaźmierczyk (7.4k34997) | answered Jun 11 '15, 8:21 a.m.
Hi Norma,
The best way to check it is go to admin panel to see Data Warehouse job status: https://your-server/ccm/admin#action=com.ibm.team.reportsManagement.etlStatus. You can see the status of ETL jobs there.

Let us know if that helped.
Norma Madrid selected this answer as the correct answer

Comments
Norma Madrid commented Jun 15 '15, 11:29 a.m.

Hi Krzysztof.

Thank you for you reply. I can see that the data collection job did not run on the day that the Sprint ended. I would think that any changes on the missed date would be picked up the next day (when the data collection job ran).

Now, because the data collection job didn't run on the last day of the iteration, does this mean that the changes would not be picked up the following day? (Therefore the burndown data not updating at all?)

2 other answers



permanent link
Katrin Heymann (19823758) | answered Jun 08 '16, 7:21 a.m.

I have the same question:

Do the data collection jobs stop collecting and updating data for iterations whose duration is over? 


Comments
Norma Madrid commented Jul 06 '16, 1:58 p.m.

Hi Katrin--

Unfortunately, once the iteration is over, any tickets closed after will not be counted towards that iteration. The workaround is to extend your iteration so that the next data collection job will pick up the change.


permanent link
Ahmed Omair (4926) | answered Jun 07 '20, 4:52 a.m.

How to get the missing data?

Your answer


Register or to post your answer.