My Release Burndown is excluding issues in its prediction

[Guy Geron]

Hi,

I have a Release Burndown that is predicting that my team will complete all issues within 2 sprints, based on 23 points per sprint and there are only 33 points left to burn.

However(!) when I look below at the incomplete issues section, it is indicating that I have 53 points left to burn.

funny enough, my Version report is including the 53 points.

Why does it happens, why there's a discrepancy? 

[Nic Brough -Adaptavist-]

Have you put story points on sub-tasks?

[Guy Geron]

Hi @Nic Brough -Adaptavist- ,

We don't use sub-tasks.

[Nic Brough -Adaptavist-]

Ok, that's the usual culprit for "burn down doesn't match story points".  I think we need to identify an issue that should be included but is not.

Could you look at the list in the issue navigator to see if there might be a pattern?

[Guy Geron]

Thanks @Nic Brough -Adaptavist- ,

I ran a query to get me the list of all items related to the fixVersion and I think I found the reason. I'd like to confirm with you that I'm correct though.

I do need to explain though our approach with setting up the boards though. 

To practice definition of ready with our delivery team, we design more than one board. The first board will have the first couple of statuses of the workflow mapped to the columns, and the board that focuses on delivering the stories has the other statues of the workflow mapped to its columns. 

We do have one status that is shared between the 2 boards - Ready for Work. By designing it like that, the team can prepare the story for delivery and signals that a particular story is ready for by moving it to that status. It is only at that point that it will show up on the delivery board backlog and can be sequence into a sprint.

What I found out going through your suggestion, is that some issues are still in the first board. Here is my assumption:

The version report and the list of incomplete stories as per the attachment is looking for all issues that are associated with the fixVersion and the board, whilst the Release Burndown is looking for all issues associated with the fixVersion and the jira project.

Are you aware of this functionality? Can you please confirm?