I'm just starting to play with JIRA.
I selected a Scrum board, team-managed.
I created Epics in the Roadmap view, and added child stories from there as well.
Within the story, I clicked on "Add a child issue". I expected it to be a "Task", but it's a sub-task.
Also if I manually create a task, and click "add parent", I only get offered Epics, not stories.
Does it make sense? What's the difference between task and story if they both seat at the same hierarchy?
Is this something I could tweak?
Thanks for posting and welcome to community and sharing your observations.
I will try to summarise and give you an overview along with details.
I hope that clarify your doubts.
Please feel free to ask else accept this answer if it responds your query.
Stay safe and heathy.
Thanks @Nic Brough _Adaptavist_ for pitching in and explaining. Much appreciated.
@Nathan Hazout - I tried to give a bigger picture with summary of related stuffs as you have asked some fundamental things. I hope this would help others in community too.
You can have a look at this if you want to know more about Advanced Roadmaps
Entire Advanced Roadmaps Documentation - https://confluence.atlassian.com/advancedroadmapscloud/advanced-roadmaps-home-998650885.html
Note - All these discussions are based to Cloud type,
Please let me know incase of any further queries or accept the answer. Thanks.
@Nic Brough _Adaptavist_ thanks again mate, spot on. I saw mail notification on this and was just about respond now but you have already answered.
Thanks @Jack Brickey also for confirming about the subscription.
@Nathan Hazout - My personal recommendation would be to pause here(accept the answer(s) that helped you so far) and put the other queries i.e. Advanced Roadmaps with team-managed projects in anew thread because it would help other community members to respond. learn, share inputs. This thread was all regarding Stories, tasks and hierarchies etc. Please let me know in case you have different thoughts.
Stay safe and healthy. Have a wonderful day.#
@Suvradip Paul I appreciate your answer but for anyone else that comes on this solution, I would advise you to clarify that these articles do not provide any insight, agile application for work management or business projects.
Ideally in business project, stories should have child "task" issue types to consolidate business work items that contribute to feature requirements or user stories. The community could benefit with clear instructions on how to build that change in Jira Work Management instead of Jira Software.
There is actually a way to work with this.
If you for example want to add tasks to a story, these are the steps I always take:
1. Create a story.
2. Add sub-tasks in the story under 'add a child issue'.
3. Add story to a sprint.
4. In your sprint board, select 'Group by: Sub task' in the upper right corner.
Then you will see an overview of all your stories including the status of each sub-task. Works like charm!
Epics are like a major grouping
Stories are parts of business value
Task is general ticket to describe something that is not a story
Sub-task is the way to divide Stories to sub pieces
If you are more visual person, I have created this pretty popular video describing Epic vs Story vs Task with example in Jira, it might help: https://youtu.be/8fLNtFJkj10
To be careful here, that is not always the right terminology. Task is a very generalised word, just "someone needs to make some effort to do this".
Jira Software's hierarchy is
But you can set up whatever names you want for many types on the issue and sub-task levels. (You can only have one Epic type)
You'll note that I specifically did not mention "task" in the examples. This is because some people will create and use Tasks at the issue level, and others will set them up at the sub-task level.
I've worked on a lot of Jira systems, of the five I remember looking at last week, two had tasks at the issue/story/feature level, two had sub-task level tasks, and one had got rid of "Tasks" completely because it was too vague a term and no-one could remember what level they were at.
It's strange that all the community discussions focus so much on Jira Software when its clear that an increasing number of users are using Jira Work Management to coordinate business projects and organize agile work process. With that said, stories need tasks underneath it so that subtasks can be within that - it's a natural way of building work projects and assignments.
We need a threat that organizes all the community members who want to learn how to build their own issue type hierarchies for grouping work tasks versus work requirements/user stories.
Is this an oversight of how Jira Work Management is used versus Jira Software? In a business project, you may have work tasks that are grouped by a user story or business driver. Then the subtasks are the checklist or independent smallest assignments that can complete that work task.
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events