Is it still impossible to apply filters to a burnup/down report from 1 board?

Fred Safian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 17, 2021

I am currently managing multiple teams on one Scrum Board and have quick filters set up to differentiate teams. I found similar question asked in 2018 (https://community.atlassian.com/t5/Jira-Software-questions/Burn-Down-Chart-filtering/qaq-p/874949) and the answer is a burnup/down report is tagged to a board. 

 

I'm just wondering if this is still the case or there are new updates that now make it possible to apply filter to a report from a single board?

3 answers

0 votes
Jonathan Hearn
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 10, 2024

<removed - not an answer>

0 votes
Fad Safian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 17, 2021

Hi all,

 

Just to provide an update on the solution that fulfills our requirement. 

Scenario: Few functional areas / teams were consolidated into 1 bigger team with a newly appointed head. Due to that, all their Jira tickets from their respective boards were consolidated into one board but by doing this, we can only generate 1 burndown report (overall). 

Problem: : Since we only able to generate an Overall burnup chart, we can't see individual team's performance in the same format. 

 

Requirement: We want to be able to generate an Overall Burnup report and able to also generate the burnup report per team within the Overall / department

 

Solution: Create the Overall 'Department' as a project and create 1 board per team and assign 'Component' to each team. 

 

So now we are able to generate Overall and each 'Sub' burnup report. 

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 17, 2021

Hi @Fred Safian -- Welcome to the Atlassian Community!

The reports are associated to the filter driving a board.  Some reports have additional filtering and I do not believe those reports do.

You note helping multiple teams.  If these are teams using scrum, I would expect they would each have sprints, and so would use multiple boards.  What is the reason for using one board?  Thanks!

Best regards,
Bill

Fad Safian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 17, 2021

Hi Bill,

Thanks for your reply. Each team used to have their own board. Due to a recent restructuring, a new department head was appointed to oversee these multiple teams and she wants to see only one burnup chart. 

Due to time constraint, we didn't spend enough time to perform our research hence we consolidated everyone into a single board and create a quick filter for each team to group the team members.

The reason why now I'm thinking of having a burnup chart for each team within the consolidated board is to visually see the progress of each team. In the case if the burnup chart is not 'fully burnt' at least I can ascertain if it is due to which team as to start my analysis. 

I'm open to other suggestions too. 

 

Cheers!

Fred

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 18, 2021

Thanks for explaining, Fred.

With the built-in burn charts and only one sprint spanning the teams, I do not see how you can do that.  You could investigate marketplace addon gadgets which support filters for burn charts, as that could help.

Another way to solve this is with a chat:

  • Consider a conversation with the new department head to explain the value teams would get by tracking work independently: progress visibility, improve forecasting, no confusion with others' work, simpler to manage, etc.
  • If successful in that chat, split the teams' boards and sprints, and...
  • Create a combined kanban board to show all the teams' work rolled up.  That would support the new department head's need to see the overall information.

What do you think?

Suggest an answer

Log in or Sign up to answer