Sprint burndown is based on the completion of Subtasks or User Stories?

[Vijay Kumar]

Hi, I am looking for some information. We have two-week sprints in our project. Team commits User stories and the sub tasks underneath. When the burndown graph is rendered in the burndown chart, is it based on status of the user story OR is it based on status of the sub tasks? Please let me know that. Because my manager is saying, it's based-on User Story. But I am saying it's based on sub tasks underneath a story. Can someone throw some light on this? I don't see an option in settings to view this information.
By the way i am scrum master i have all the privileges, except JIRA board admin. 

[Trudy Claspill]

Hello @Vijay Kumar 

Based on my experience working with Scrum boards the Sprint burndown is not based on subtasks. It is based on the parent issues transitioning to a status in the right-most column of the board.

[Vijay Kumar]

@Trudy Claspill Thank you so much for the reply. Appreciate it.

Is there a way I can check that info in settings?

[Trudy Claspill]

It is not a configurable setting, so no, it doesn't appear in any of the settings screens.

[Vijay Kumar]

@Trudy Claspill  Sure...not a problem...Thank you for the reply though.

[Danut M _StonikByte_]

Hi @Vijay Kumar,

Indeed, the Jira's burndown chart is not based on sub-tasks; it is based on parent tasks (stories, bugs, tasks. etc).

If you want to track by sub-tasks, you will need a plugin from Atlassian Marketplace, like for example, our Great Gadgets app. 

Danut.

[Vijay Kumar]

@Danut M _StonikByte__ Thank you so much for the reply. This clears my all doubts. Appreciate your help.