How to monitor subtasks in burndown chart vs issue count

[Eric Mosse]

I have several tickets that are assigned in a sprint. My team breaks each r ticket into subtasks. When I got to the burn down chart, I can see each ticket in the issue count. However, when I go to tasks, it just a straight line at 0 and there doesnt appear to be any subtasks reflected in the chart. 

The reason I am doing this is to better track each day how we as a team are progressing daily on each major ticket. Ideally each subtasks takes a day or so. And by monitoring the subtasks, I can see our daily progress/effectiveness during the sprint.. Is there an easy way to do this with the current burndown chart? Or do I need to change how our process is to monitor our progress on each item?

[Nic Brough -Adaptavist-]

Burndown is trying to measure delivery against commitment.  You commit to do a set of stories at the beginning of the sprint, and you burn down the points on a story when it is complete.

Sub-tasks are irrelevant here.   A story is only done when all its sub-tasks are complete, doesn't matter if there's 0% of them done, 1%, 50%, 99% - those stories are not done, so you do not burn-down on them.

I understand the desire to see progress overall, but that's not what a burndown chart is for.

[Eric Mosse]

Thanks. Is there an alternative for this to track subtasks?

[Nic Brough -Adaptavist-]

Simple approach would be to use the "created vs resolved" chart, maybe with a filter like "issuetype in subtaskissuetypes() and sprint in opensprints()"