RTE in a Burndown Chart is not zero at Sprint End

Question

We have a workflow where the Remainig Estimate is automatically set to 0 minutes upon Sub-task completion.

The problem we are facing is that the Remaining Time Estimate on the Burndown Chart is not at 0 at the end of the Sprint even though all stories were completed

If you look at the picture, the RTE stays at around 1w 3d - this is exactly the SUM over all Sub-tasks of the difference between Original Estimate and Work Logged.

Can somebody explain this behavior and offer an advice on how to improve?

antonsarov · Answer

Hi Earl,

thanks for the suggestion! I have corrected the workflow as you proposed and will observe the behavior. If everything goes smooth, I'll mark the answer as accepted.

I realize that this is an error on our side but given the fact that we followed the guide mentioned in the KB, I still find that this information should be there in the first place. I expect that other people may stumble upon this as well.

Best regards

Anton

Earl McCutcheon · Answer

Hey Anton,

Thanks for the screenshots, and it looks like a post function order conflict.

You will want to move the #6 post function that clears the Remaining Estimate Field so that is is above #4 which generates the change history item.

The Report is pulling the value from the change history which has the value present at that point and then indexed with the value present but removed after these actions occur.

Also in post function logic you always want the last two Post function events to be in the order of the Reindex event then the Fire Issue Event function, this can cause odd rendering issue on the issue view and data collisions if a field is modified after the index is updated as in the current odder the index has the valued stored in the field but the data was cleared in the backend by the post function events.

Set up the post functions like this and you should be good:

Regards,
Earl

antonsarov · Answer

Hi Earl,

the post functions are defined like this:

Except Number 6, all the other post functions are the "standard ones" that come with the Software Simplified Workflow for Project...

We are not using any add-ons, we just created this post function manually.

Is there a difference if you leave the field "Remainig Estimate" blank or set it to 0 when you create the function? With the empty field the Time Tracking of an item looks a bit strange, having Remaining as "Not Specified":

Thanks,

Anton