Can Burn Down Gadget be configured at a Sub-Task Level?

[Jacques Larose]

On a Dashboard, the burn down gadget is determined how the project Board is configured. Seems to be only at a story level but looking for confirmation. Story Points burn down when stories are done, thus reducing the total points. Seems that Issue count is based on story level also and burns down as stories are closed. Also looked at original estimate (but don't want to log time spent or remaining time). 

Looking for ways to track sub-tasks in process during the sprint using a burn down. Any ideas?

[Petter Gonçalves]

Hello @Jacques Larose

Thank you for reaching out.

The burndown gadget is based in the burndown report, which is configured to only include estimation from the parent issues (Stories) and not sub-tasks. This behavior is described in the documentation below:

View and understand the burndown chart 

Story Points on subtasks are not included in the Burndown Chart. (Only Story Points on parent tasks are included.)

We have a feature request opened that provide the reason why the burndown report (and all other agile reports) only consider the estimation of Standard issues:

Sum estimates from sub-tasks in user stories 

That being said, I suggest you to properly estimate your issues using the parent (Story) issue type to properly track your work in Jira.

Let us know if you have any questions.