nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reports : sprint/burndown do not show completed tickets

unknown

In Reporting, for previous Sprints I see no "Completed Issues" in the Sprint or Burndown chart. This is despite the fact that many tickets were completed during the sprint.

PLEASE HELP!

Thanks.

My workflow and resolutions:

Screen Shot 2017-07-01 at 4.13.54 PM.png

My board setup:

Screen Shot 2017-07-01 at 4.12.10 PM.png

Sprint Report Example- Notice no "Completed Issues" section.

Screen Shot 2017-07-01 at 4.09.30 PM.png

Accepted answers

Nic Brough -Adaptavist-

It's the end of your board filter.

A board, and hence its reports, need a filter to define what to look at. You've told your board to ignore closed issues. So it can't report on them.

You need to drop all the sprint related stuff in the filter. JIRA is already trying to handle that for you, you don't need any of it and it's breaking your reports.

All comments

Ignacio Pulgar

Are there more boards which display those issues?

If that's the case, do all of them have the 'Completed' and 'Sign Off' statuses mapped to the most-right column? This would be a typical cause of story points not being burnt.

unknown

I have done as advised and made sure all boards that view tickets for this project have those status mapped to the last column.

Could it be my board filter?

project = <ProjectName> AND (assignee not in (<ilst of people to ignore...>) OR assignee is EMPTY) AND (sprint in (openSprints(), futureSprints()) OR Sprint is EMPTY OR sprint in (closedSprints()) AND status not in (closed, completed, "sign off")) ORDER BY Rank ASC

Nic Brough -Adaptavist-

It's the end of your board filter.

A board, and hence its reports, need a filter to define what to look at. You've told your board to ignore closed issues. So it can't report on them.

You need to drop all the sprint related stuff in the filter. JIRA is already trying to handle that for you, you don't need any of it and it's breaking your reports.

unknown

that was the trick - thanks!

Sara Lufrano

I think the issue I have with my burndown chart is caused by this but it might also be that it isn't taking subtasks into consideration.

I don't understand how to update or even look at what the burn down chart filters are. Can I get some direction?

Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-core

report