Why isn`t JIRA supporting by default the hierarchy "Story-Task-SubTask"?

[Catharina Zorc]

I have in my current project the problem, that I cannot have the hierarchy Story-Task-SubTask. we can only add a SubTask to a story. So we have much Subtasks to one story what makes the whole JIRA confuse, but we also cannot use the burndownchart. So why is "Task" by missing. I had it other projects where it was not missing. 

[Catharina Zorc]

No the issue type is available but I cannot assign it to a story. As a result, all my projects are incredible confusing. I have one story and many subtasks which are not even pictured in the burndownchart. But to complete a whole story in a sprint is in our setting not possible. SO the burndownchart is useless but the team would like to see their progress. And I would like to see a clear structure. First I am totally confused that this is not a possible. Is there any simple way to create an "4th level"? 

[Laura Campbell _Seibert Media_]

This is normal that you can't assign a Task to a Story. They are at the same hierarchy level and can't "own" each other. If you cannot complete a Story within one sprint, what about moving that information to an Epic, and breaking down the feature into more Stories so that one or more can be completed within the sprint?

If you need more than 3 levels of hierarchy, check out Advanced Roadmaps or apps like Structure.

Additionally, subtasks are not used in the burndown chart. See this discussion for someone who had a similar need: https://community.atlassian.com/t5/Jira-discussions/Burndown-chart-on-Subtask-level/td-p/2249868

[Laura Campbell _Seibert Media_]

Hi @Catharina Zorc and welcome to Community.

The native hierarchy of issues in Jira is Epic - Story/Task OR any other issue type you create - Subtask. Stories and Tasks are considered to be at the same level in the hierarchy.

Can you clarify if you Tasks are missing from your project (as in, the issue type is not available) or if they are just missing from your burndown chart?