So after my researching on this forum and other places, my conclusion is, that Jira doesn't want us to add a task under a story. Given the generally accepted scrum hierarchy Epic > Component > Story > Task > Sub-task, a Jira user will naturally want to see in his sprint board with a story above its tasks above their sub-tasks. In Jira it's only possible to visualize those elements together
A Story and its Sub-tasks, which looks like this:
A Task and its Sub-tasks
Can anyone (from Jira) explain the reasons why doesn't Jira allow the visualization of tasks below a story?
in Agile you have Epics that group together (user) Stories and (as far as I'm aware) Tasks in Jira are allowed (with all the other custom issue types) so you can add your own maintenance or non-developing related actions.
There's no plan to introduce more hierarchy than Epic > Story/Bug/Task/Other > Sub-Taks/Other
However, should you want infinite hiearchy, you can try https://marketplace.atlassian.com/apps/34717/structure-project-management-at-scale
I hope this helps a bit.
Thank you @Krisztian Kovacs for the clarification of the common used hierarchy. Totally agreed with you there
But that does not exactly answer my question, which is about why can't you sub-order tasks below a story, which seem natural to a lot of Jira users. (I edited my question with some "text visualization")
Why do you see Story and Task on the same level in "Epic > Story/Bug/Task/Other > Sub-Taks/Other"
I thought the structure has 4 levels like this: Epics > Stories > Taskes > Sub-Tasks
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event