Sprint Burndown Company Managed and Team Managed

[Luis Dominguez]

Why is the sprint burndown report reporting different in the team managed project board compared to a company managed board? For example, in the team managed board the burndown report shows the stories completed with an Epic and the progress towards completing the sprint.

An Epic with 5 stories, 3 completed, the report shows 3 out of the 5 completed for that particular sprint.

The burndown report, in the company managed board, only shows an issue completed if all the issues in the Epic are completed. 

Is that how the reports are supposed to work? Why are they different?

[Trudy Claspill]

Hello @Luis Dominguez 

Can you provide screen images of the two reports you are referencing?

[Luis Dominguez]

[Luis Dominguez]

Hi Trudy,

I have attached a screenshot of the report above. It is the same report in both a team managed and company managed report but the reporting works differently: on the team managed board the report shows a count of child issues of an epic as completed. Where as in the company managed report, the report only shows issues as completed if the entire epic is completed. Why is that?

[Trudy Claspill]

Hello Luis,

I am not seeing the same thing as you in my instance.

In a Company Managed Software project I create a scrum board and add base level issues (story, bug, task) to a sprint. These issues are child issues of an Epic in the same project. When I move the issues to the right-most column of the board, the burn down chart reflects the issues are burnt down.

When I do the same think for a Team Managed Software project, I see the same results.

The right-most column of my board is mapped to a green/Done status.

Issues that are not in the right-most column are not considered complete. They will not be burnt-down on the burndown chart until they are moved to the right most column.

Whether or not a completed issue is a child of an Epic should have no impact on the burndown chart. I suspect that there is some other factor that is impacting the apparent burndown of the issue count.

It would be helpful to drill down into a more specific case where we see the issues in the sprint and correlate when they were transitioned to the final status (right-most on the board) against what is showing in the burndown chart.