Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Add Parent as User Story to a Task

Ashwini Syamanur
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 5, 2024

The task is not taking user story as a Parent. It is taking Epic as a Parent 

4 answers

4 accepted

4 votes
Answer accepted
Robert Wen_ReleaseTEAM_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 6, 2024

Hello @Ashwini Syamanur 

Are you creating SubTasks in your User Story or creating Tasks?  There's a difference.

A Task is a Standard Issue Type, which is at the same level as a Story.  Tasks can never be children of Stories.

You can create SubTask Issue Types (the default is SubTask) which can be children of Standard Issue Types.

Eugenio Onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 7, 2024

@Ashwini SyamanurAdding to what @Robert Wen_ReleaseTEAM_ shared, you can LINK tasks inside stories, but they cannot be child.

The link below shows a great overview about it:
https://www.atlassian.com/agile/project-management/user-stories

0 votes
Answer accepted
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 7, 2024

@Ashwini Syamanur -

As I agreed with other community leaders' suggestions, keep in mind that "User Story" and "Task" issue types are at the peer level in Jira/JSM env.  Typically, one will use "Sub-task" issue type to conduct the necessary roll-up against an issue type of "Standard Issue Type" category.  

As related to Issue Hierarchy configuration (it is a part of Advanced Roadmaps for Jira) which one can create higher level issue types for Epic issue type to roll-up against.  Out of the box in Jira Software (without the usage/setup of Advanced Roadmaps for Jira), the standard hierarchy is 

Epic

>> Story, Task, Bug etc...

>> > Sub-task (note even though Epic is a parent of Story/Task etc.., it can also rollup directly against the Epic issue type.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

0 votes
Answer accepted
Evgenii
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 6, 2024

Hi, @Ashwini Syamanur 

In Jira Cloud, users have access to a feature called 'issue type hierarchy.' This feature enables users to define which issue types can be parent issues. However, this functionality is exclusive to the Premium plan. On the Standard plan, 'Task' and 'Story' are on the same hierarchy level, and this cannot be altered.

Here you can see how it looks like in Premium:

Screenshot_5.png

0 votes
Answer accepted
Eugenio Onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 6, 2024

Hi @Ashwini Syamanur

This is directly related to the Issue Type scheme you have defined for your project.

Would you please send some screenshots so we can help you further? Are the tasks being created inside the Story as sub-task or are you creating tasks by importing them?

Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events