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; } } }

If I use two boards in the same project, can I filter the Burndown chart by board too?

Thiri Aung_x91hd5

I am using two boards in a single JIRA project according to this, and used different filters for each board. Is it possible to filter 'Burndown chart' by same filters as well?

For example, Board 1 is filtered for Assignee A, and Board 2 is filtered for Assignee B. And when I go to Burndown chart report, I want to see the report for Assignee A only if I choose Board 1.

Comments

Mohamed Riza _ServiceRocket_

Hi @Thiri Aung

The Burndown Chart is board specific rather than project specific. Therefore the report would in Board A will only be for Assignee A.

Thiri Aung_x91hd5

Hello, thank you for your comment. The problem I have right now is although I have two boards, the Burndown chart is showing the same data no matter which board I chose. That means, when I chose Board 1, I can see both A and B's tasks. How should I fix this problem? Thanks.

Mohamed Riza _ServiceRocket_

@Thiri Aung

In this case, I would ask you to first open any issue that is showing up on both boards. Check the values in the *Sprint Field*. Does this with Assignee A attached to a sprint from Board B? If so, this could be the reason why you are seeing this issue in both reports.

If this is not the case, then you would need to do a lock reindex in Jira as this may just be an issue with corrupted indexes.

Thiri Aung_x91hd5

Hello, thanks for your reply. Both board 1 and 2 are for the same Sprint. But Assignee A and B are assigned on different boards.

Does that mean, if it's for the same Sprint, we can't see the difference in the burndown chart no matter which board we selected?

Thanks.

Welcome!

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

Quick Links

Find more posts tagged with

agile

board

scrum

burndown