Yes, exactly something similar to the below structure.
Although this logic might cause some conflicts this is how Jira is considering the hierarchy of the issue type.
For instance, while generating a report at the end of each sprint, the estimation you have given to the tasks won't be included in the reports.
According to this poster, you are incorrect, and this feature has been added: https://community.atlassian.com/t5/Jira-questions/Re-Re-How-to-add-task-to-a-story/qaq-p/718744/comment-id/234478#M234478
However, the moderators have locked the thread, so no-one is able to ask that poster HOW you achieve this in JIRA today.
@Picme App, that is a long post. Are you referring to Chris’ comment or some other. Chris is referencing the use of sub-task to a story not task to a story.
Regardless, this question is still open so if someone happens to have an answer counter to mine they can certainly post it here. Too you are free to post a new question on this matter to potentially drive new input.
Work item is no where near Epic proportion, thus it's a User Story. Need to assign a piece of the User Story to another worker, so creating a task allows that additional assignee to create sub-tasks for his work efforts if desired. Both assignees can be working concurrently.
If we create sub-task from the outset, 2nd assignee can't make use of the sub-tasks to manage their piece of the work item.
Having these recorded as such also help future development for similar issues, so we want to see the steps involved from that second assignee.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
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