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?

The additional of the 'refine report' functionality would be a huge benefit on all the scrum board reports.

We have several generic boards with quick filters to restrict the details by team. This works really well in the plan and work mode but when looking at burn down charts for example, we are unable to view progress by team due to the lack of quick filters.

I would love this.

As a workaround, I am forced to create separate Agile boards for each specific burndown chart I want to see. This is very cumbersome. Having these Quick Filters would make it so much easier. Quick Filters are there on Plan and Work modes, so it seems a no-brainer to also add them to Report mode!

Personally, I would expand this story to implement the "Refine Report" functionality on the Cumulative Flow report.

I would like to see an option to render the report as a multi layered area graph (like the cumulative flow), with each layers representing the 'remaining effort' for an individual swim-lane.

This way when using the Assignee as the swimlane we can see the workload placed on an individual in a glance.
Alternatively if the horizontal swim-lanes are used to represent components, the user can see the burndown for a specific component.
~James

Yup, this seems like a no brainer, and would be very useful for us too.

Thanks!
-Johnny

Are there any plans for this one?

A must-have for us too.

+1. Thank you Steve for suggesting this workaround. However I do think that the Quick Filters should be available for the Burndown Chart on the Board as part of the Board's design. I am surprised and disappointed they are not at this stage.

Also this method can be extended to show a burndown for any filter so I think it will help other people's request as well.

+1 for this.

+1 from me. So far we are using filters for the Plan- and Work-View. The Scrum-Board contains the stories of 4 different teams, so the burndown shows actual the progress of all teams together. If i could configure a simple team-filter i would be happy. I tried the following to help myself: I created 4 teamfilter and created 4 Scrum-Boards. Each ScrumBoard filtered on a team. Disadvantage: No product-overview. And our sprint is synchronized over all teams together. Creating the same synchronized Sprint 4 times in every Board-View will end in a mess.

this would be very helpful. so far I achieve this by creating a filter and then separate board for purpose of Burndown chart only! But it gets tricky with non-working days configuration, as it needs to be applied to all such "extra" boards

+1 on this feature.

I have several projects going on in a single sprint and I would like to be able to view how each one if burning down so that I easily know where to focus with the team. Burndown on an individual engineer would also be interesting.

I agree, this is a very high priority. Even with only two teams working on one project, the current burndown becomes pretty useless.

It would be nice if there was also a better chart so that it looks more like a typical burndown.

Definitely, a must-have.

Same here, that's really a must-have!

I second this; would love to see a burndown chart based on a certain theme, or a certain assignee.