Every now and then, the question pops up, why does atlassian invites to use subtasks, but they dont show in the Burndown chart.
The answer is: no, that does not work. Some people help themselves with add ons and twisting and configuring them, that it somehow works out.
But until now, Atlassian did not provide a simple solution to that simple demand.
However, my personal solution is, that I reorganize my projects and boards in a way, that a story/task is the lowest level in my boards. As they are shown in all charts when closed, they need to be refined as much as possible, to have a chance to be set to done in one single sprint.
Enjoy!
It is important to understand what Atlassian is doing with Jira Software. It supports Scrum and Kanban, of course.
But the implementation of sub-tasks is a bit of a hangover from the original "scrum" process (and totally accurate for Kanban) whilst trying to not to annoy people doing Waterfall.
Sub-tasks are not sprint items, they are a fragment of a sprint item. So you should not "burn down" on them. Burn down is for sprint items.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.