Burndown chart for number of sub-tasks remaining in sprint?

[Jeremy Martin]

My company recently upgraded to a newer version of JIRA.  Previously, we had a burndown chart on our dashboard, that tracked the number of sub-tasks still open in our current sprint.  With the new(er) version of JIRA, we can't seem to configure the burndown chart the same way.  We can do number of stories, or number of story points remaining, but not number of sub-tasks.

Using, eg, number of story points remaining doesn't work as well.  You can't close a story until all of its subtasks have been closed, peer reviewed, etc.  And my company has a lengthy process for peer reviewing and testing stories before they can be closed.

So for burndown charts using remaining story points, or number of remaining stories, the line doesn't start to come down much at all until at least the 2nd week of our 4 week sprints.  With the sub-task burndown chart, the line would start coming down the first or second day of the sprint.

Any way we can get the old subtask burndown chart back?  Thanks!

[Danut M _StonikByte_]

Hi @Jeremy Martin2 / @Carmen P ,

In the latest version of our Great Gadgets plugin, the sprint and release burndown gadgets have an option to include sub-tasks, which you could use to achieve what you want.  The plugin is available for both Jira Server (https://marketplace.atlassian.com/apps/1218777/great-gadgets-for-jira-server?hosting=server&tab=overview) & Jira Cloud (https://marketplace.atlassian.com/apps/1216564/great-gadgets-for-jira-cloud?hosting=cloud&tab=overview). 

Danut.

[Carmen P]

Our company would also like to have this feature back.  We used to track subtasks in our burndown chart until we switched to using JIRA because we don't track in time estimates but rather we use Story Points.  I found another suggestion here to work around this.  But it requires to use time estimates: https://answers.atlassian.com/questions/17436843

[Jeremy Martin]

EDIT:  I found another answer suggesting that this is (no longer) possible:

https://answers.atlassian.com/questions/17436843

I know the old version of JIRA/GreenHopper that my organization used to use had this capability.  Why was it removed?