Hello, another vote for this issue. It would be helpful and convenient to self asses your own workload.

+1

+1 please add!  Very helpful for individual contributors/assignees to be able to see their own burndown charts as a quick visual 'biofeedback' mechanism

+1

+1

Will add my voice here. Given our configuration of Jira, we would like to be able to filter burndowns on dashboards.

Forget about it, this ticket was opened a DECADE ago.

Atlassian has failed so hard on its customer satisfaction... This is the second product I dropped in my different companies. Before SourceTree for Fork, now Jira for Linear.

Best solution other than waiting for this ticket to be done: abandon this dead zombi-land desert company.

+1 from me as well. This is a very good idea.

+1 for filtering based on teams -> this would avoid duplication for multiple subboards just for the need to get a report

+1 for quick filters on Sprint Burndown, Version and Epic Reports.

Yes, this would be SUPER helpful to filter on "routine maintenance" items from our burn down so I can see how our "feature development" items are burning. And plenty of other use cases.

Massive +1 for quick filters on Sprint Burndown.

+1 Looking for burndown based on labels or users

Any status regarding filtering the Burndown Chart, at least per user?

This would be highly valuable feature!

I want to show a burndown-style chart on my personal dashboard, that lets me know how I am doing compared to the expected sprint burndown "guideline". Am I ahead of the curve or am I falling behind? Should I say no to new tasks or do I have time to take on a couple more? Maybe I should give away a few tasks to someone else that have the time?

I find it very surprising and disappointing that Jira does not have this capability already.

Voting for this! +1

+1

+1 would like to see this by Component at least 

+1 allow for the same Quick Filters on the Reports as are used on the Active Sprint board 

+1

Major items we need filter of burndown charts by include: project team (we use Tempo), assignee, and release (fix version). Other custom fields would be nice to have as well. 

+1

 It's strange that this feature isn't embedded to Jira...

+1

+1

+1 
Need this ASAP

We are looking for a feature like this too! +1

+1

+1

This would make me very happy

+1 on this request ... I use one project and use Quick Filters to divide work for multiple teams. I would like to create a separate burndown for each team.

Ive been getting a lot of demand for this feature from our engineering managers

please. this is badly needed

Yeah, I think this would be nice to have too. Being able to view issue burn-downs per user or feature would be great. Creating a whole board to work around the issue is a PITA.

If any other votes count (mine is 360th), I would really like to progress this request. It's disappointing that is is still gathering interest and hasn't been accepted after all the votes ...

Please bring this back, I cant believe this was removed!

Ridiculous that this USED to be a feature, and is now removed.  It's literally ONE click in Hansoft.

Please give us this most BASIC of functionality.

I'm on 7-8 years now, and I disagree. It hasn't always been this way. A product doesn't get this big without valuing feedback. To stay big you need to keep valuing it. That requires people to keep giving it..

Amanda, it's their business model.  We've been using them for 5 years and it's always been this way.  I'm afraid I wouldn't expect it to change anytime soon.

Atlassian I'm starting to get annoyed finding out I need a plugin for so many things that should be prioritized for the core product.

As an alternative, assuming you are using versions later than JIRA 6.x, use this gadget on a dashboard:

https://marketplace.atlassian.com/plugins/eu.mirrorlake.plugins.pc2d/server/overview

It's query driven so you will need to make a bunch of queries, but it will at least give you what you need. If you are using JIRA 6.x then you can use the agile classic burndown gadget to do the same.

I've just come back to JIRA after 5 years away. I'm setting up dashboards for my team with burndowns for current user and one for me showing the whole team's burndown for issues in our components and current sprint. After a few tries and some googling I ended up here discovering that I can't 

We are not upgrading to JIRA 7 because our projects need this functionality that disappeared with the Rapid boards. So we have to stay on JIRA 6.4 to be able to use the (old) Classic Burndown gadget. Please add this functionality so we can keep up with your good work.

Has there been any updated response from JIRA/Atlassian since December 2015? This feature is really important and useful.

Haha, 5 years already and still stuck in progress - that is what mean to be Agile, Atlassian! 

So agile so you can stretch critical feature into 5 years and still not deliver.

Hi,

yes, I also vote for the possibility to customize the filterquery that selects the issues shown in a burndown chart.

That seems not to be a too heavy thing to implement.

All,

While i still think this should be addressed, the workaround I am currently using is creating a board for each filter i would like to see.  That way i can see the burndown for that filter.  This is only manageable if you have a small # of filters you really care about ...

This is an essential tool for me. The only way to do this now is to export my filtered search results to Excel and produce a graph there. Not ideal.

shame on the product owner, this is so important feature and it's been 4+ years since its creation. 

Any update on this?

I would also like to request for addition of filter in burndown chart. Individual burndown will help to find out how team members are burning work on daily basis.

So let me get this straight. You had this feature in Agile Classic. Then you discontinue said feature and don't offer any replacement to the people that were using it.

Creating burndown charts is a hugely important feature and they should be flexible and easy to create / use. Ideally you could apply live filters to them and alter the start & end dates independently from the sprint or fix version.
I imagine a feature like this would make a lot of people very happy. Now if only Atlassian would be in the business of making its customers happy...

can we not just add the filter logic to the burn down char?

The development team I work on would greatly benefit from the ability to filter the burn down by developer so that we can load balance and identify risks. This function seems table stakes to me so I am a little baffled why it is not yet implemented. Please scope it into a future release and let us know when we can expect it. Thank you!

We have too many projects to create too many boards in order for this to work for us. This feature would be extremely useful. 222 votes and counting. Is this on the roadmap to be implemented?

I'm trialling Jira right now and I agree this would be extremely useful.

This suggestion was filed about 4 years ago and still no implementation.
When can we expect this to be implemented?

+1 Specifically we would like the ability to quickly filter a burndown chart to a given project and/or component, much like the current "Release Burndown" chart where you can choose the release version, but with project and component instead.

+1

& ideally this would be further extended to be completely independent of sprints, where start & end dates for the burndown are optionally specified within it vs. having to rely on hardcoded ranges set in a mandatory sprint.

the current implementation of sprints is so incredibly limiting that optionally decoupling burndowns from it is likely a clearer path forward than than iteratively attempting to retrofit sprints into accommodating all of its shortcomings.

In my case the problem is that we have few hundreds of developers working on a project.
Creating, maintaining so many boards is impossible.
I NEED THIS FEATURE!
172 votes for feature and still no implementation.

Gotcha. Thanks

My Agile burndown chart gadget does not allow me to use quickfilters too
Key point of this workaround is the creation boards for each members:

• Main bord has filter project = "project_name". This boar for all members. It contains all tasks. It named "Main board"
• 1st developer board has filter project = "project_name" AND Sprint in openSprints() AND assignee = "1st developer user_name" It named "1st developer"
• 2nd developer board has filter project = "project_name" AND Sprint in openSprints() AND assignee = "2nd developer user_name" It named "2nd developer"
• ...

I set several board's names in each Agile burndown chart gadget after boards creation.

You should't switch tasks between developers. In other cases you will have wrong data on burndowns.

I think i might be missing something but My Agile burndown chart gadget does not allow me to use quickfilters

Gonçalo Antunes, you can create boards for for each team member.
I use filter project = "project_name" AND Sprint in openSprints() AND assignee = "user_name" for each member board
After it you can create dashboard with Agile Sprin Burndown gadget and Workload pie for main board.
I have one main board and 6 member board now

Uhmmm how is this not implemented yet? With broken classic burndown chart and the non action on GHS-6702 why not add this and fix the problem?

Created 2012 and still not implemented yet.

We are currently using the classic view and rely heavily on the burndown chart for a fast status and prediction of hitting the target date. We have a filter for each team member so we can quickly look to see how each member is doing - adding to their estimates, burning down the work etc.
But with the latest version, that feature seems to be missing. It's critical to managing the work of a large team.
Rob Mitchell
Merge Healthcare.

I agree. We'd love to see this added. It would be highly beneficial for our team.

Yeah! I totally agree that this feature will help most of us and most importantly the management. Thus, this will help in improving efficiency specially for better team velocity and performance evaluation.

Jas from NOKIA

The implementation of this feature would greatly help us on a more detailed and efficient way of monitoring our progress in our daily work.

Erwin from NOKIA

I second for the proposal which will improve the efficiency of Agile work.

Thanks for watching, voting and commenting on this Suggestion.

We see it as a valid Suggestion, however we cannot provide any guidance at this time as to when we'll be implementing it.

Regards,
Martin
JIRA Agile

Curves must be easily seen.
Deadlines make us stronger.

This feature will surely help both the management and employees. Better team velocity and performance evaluation which helps in improving efficiency within sites. Hope it gets implemented soon.

Tom Jordan from NOKIA

This would be very beneficial and efficient.

Faith from Nokia

This feature will surely ease our work in tracking the burndown chart.
Kristian from NOKIA

Saves us the trouble of tracking our burndown chart manually.

This feature would certainly make our job easier. I'm sure other users will agree.
Kenneth from Nokia

This would help alot of Jira Users
Greg from Nokia

This feature will help a lot.
JM from Nokia.

Hi guys if You work in the projects You can ask Your colleagues to vote for this issue. That is what I did.
Together we can make it happen
Piotr from Nokia.

I share similar emotions.
I must say Jira is very bad at reports.

I'm dying for this feature!

I'm dying for this feature!

+1. There are so many scenarios where this would be useful, for example here's a few:

1. Sprint burndown report filtered for single member, or subset of a team
2. Version report filtered for in any number of ways to answer "what if" questions regarding the completion date. E.g., 1) Only items in a sprint, but not in a backlog. 2) All items plus all items in one epic in the backlog. 3) Completion date per person. 4) Many more...
3. Ditto for epics

+1. We would love to see this happen!

I would love to see quick filters by assignee, by issue type etc. coz we have cross functional team members as part of one product team and I wish to see the Dev / QA / Doc velocity per Sprint or over a period of time. Since these members belong to same team and working on same set of epics (features), I think filter is the easy solution to this problem. Viewing in the issue navigator means I have to do manual calculation of story points on the filtered data, will not be able to see graphical representation and many other shortcomings.

+1

+1

+1

+1 more

Just to put some life into this issue.
We are rolling out large project tracked with Jira. 40+ scrum teams and no possibility of filtering of burndown chart.
How many votes do we have to gather to push this one forward?