Add Parent as User Story to a Task
Asked by Ashwini Syamanur:

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


Answers:
author: Robert Wen_ReleaseTEAM_
body: Hello [@Ashwini Syamanur](/t5/user/viewprofilepage/user-id/2571787)

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.

comments: author: Eugenio Onofre
body: [@Ashwini Syamanur](/t5/user/viewprofilepage/user-id/2571787)Adding to what [@Robert Wen_ReleaseTEAM_](/t5/user/viewprofilepage/user-id/3970316) 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>


author: Joseph Chung Yin
body: [@Ashwini Syamanur](/t5/user/viewprofilepage/user-id/2571787) -

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.


author: Evgenii
body: Hi, [@Ashwini Syamanur](/t5/user/viewprofilepage/user-id/2571787)

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](https://community.atlassian.com/t5/image/serverpage/image-id/299206i108E682C53C094B0/image-size/large?v=v2&px=999 "Screenshot_5.png")


author: Eugenio Onofre
body: Hi [@Ashwini Syamanur](/t5/user/viewprofilepage/user-id/2571787)

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!


author: Shakoora Maknoon
body: Hi  

I find that Tests using XRAY should be able to link to the story as one unit deliverable piece of work. At present, the standard plan is that the test can only be attached to the EPIC as the parent. I disagree with this standard plan or design; as an EPIC is a larger initiative made up of several unit pieces of work which are denoted in the story. As such, the test would always link to a Story.   

I would really like a change in this design as XRAY and JIRA support team said this is not possible.  

Thanks


Tags: cloud

jira-service-management

jira-service-management-cloud