Iteration Burndown Report Still Showing Work To Be Done

[David Cronin]

Telerik,

I am using TeamPulse 2011.1.504.0.

I have a burn-down report that isn't hitting 0, despite all my stories being marked as closed and my tasks likewise.

What is involved in the burn-down calculation? Is there anything I should be looking for?

[David Cronin]

I do have one thing to add. When I checked TFS, I found 3 items there that were in TFS and not in TeamPulse.

To delete a task, I have been unsyncing from TFS, deleting the task, then re-syncing to TFS. This apparently abandons the task in TFS but it doesn't show up in TeamPulse anymore.

In case this helps you figure it out, I thought I'd let you know.

I deleted the task from TFS via the API.

[Robert Régnier]

Hi David Cronin,

 Regarding the deletion of tasks, TeamPulse does not hard anything in Tfs which is why the delete option is disabled when a story is syncing.  The preferred approach is to mark the status of the item as Deleted.

Regarding the burn down not hitting 0, this might happen if for example you had a story for Iteration 4 that was set to done after the end of the iteration.  Because the burn down chart is constrained to the start and end dates of the iteration, the post iteration status change of the story won't be picked up.  Such a status change would show if you viewed the burn down for a parent iteration.  Might this be describing your scenario and explaining what you are seeing?

Kind regards,

Robert Régnier
the Telerik team