Gap In Burndown Chart

Robert Carter (429●2●85●89) | asked Jul 29 '16, 4:54 p.m.
edited Aug 01 '16, 12:35 p.m.

During our upgrade process after a few days we noticed the data warehouse was not getting updated after the upgrade.

The upgrade was done on July 9th. And we restored the DCC and data warehouse jobs on July 20th. On our burndown charts we noticed the gap in data from July 9th to July 20th. We changed the 'Delta Load Configuration' to July 8th. Thinking this would grab data from July 8th through today.

The jobs ran successfully and the ETL logs show that it was attempting to get changes since July 8th. Any ideas as to why we still have the gap in data?

Comments

Robert Carter commented Jul 29 '16, 5:46 p.m.

Do the Data Warehouse Jobs need to run every night to pick up Burndown data? Or can they be run to 'catch up' on failed runs? For Example using the 'Delta Load Configuration' to pick a date when it last ran successfully.

Robert Carter commented Jul 29 '16, 10:14 p.m.

So according to this article...

If team members do not update their data by the end of each day, the status of their work items will not be properly reflected in the report. Although updating the status of their tasks will help the trend line to catch up at the next processing point, there is no way to update the history. The task will show as done (finished) on whatever day it is closed, not whenever the work was actually finished.

So, if the data warehouse jobs don't run for a couple of days or fail. Then there would be no data in the burndown chart for those days and there is no way to get those back dated events?

Be the first one to answer this question!

Register or log in to post 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.

It's all about the answers!

Related questions

Gap In Burndown Chart

Be the first one to answer this question!