How to create Sub user Stories under Story issue Type?

[Bala Krishna]

Is there a way where i can select Issue type as Story when i click on Create sub Task option from More Menu. as of now i am gettting this tool tip in"Create SubTask window"

Some issue types are unavailable due to incompatible field configuration and/or workflow associations.

[Renjith Pillai · Accepted solution]

While I didn't completely understand this, if you need to have Story as a sub-task type, go ahead and create the new sub-task type and called it Story or rather Sub-Story (else you will get confused yourself later on)

https://confluence.atlassian.com/display/JIRA/Configuring+Sub-tasks#ConfiguringSub-tasks-Creatingasub-taskissuetype

Also dont forget to associate the newly created type to the issue type scheme. https://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects

Is this what you are looking for?

[Bala Krishna]

Thanks for your help Renjit. I dont want to create new sub-task type as Sub-Story. Basically i want to maintain this structure in Jira .. Attached here

We are using EPIC but just want to know is it possible to implement this way in Jira.

[Renjith Pillai]

No, that is not possible. What is possible is three levels

Epic -> Story -> Technical Task (or any sub-task type)

[Bala Krishna]

LOL. I think i should live with this structure. Epic -> Story -> Technical Task (or any sub-task type).

Thanks Renjith.

[Renjith Pillai]

Native JIRA supports only two levels. With GH you get an additional one Epic. So if you are okay with calling "Story (Functional US)" as an Epic, yes, it is possible.

[Bala Krishna]

Thanks. :( Let me ask one more Q for my learning purpose ..How about this

Story (Functional US)--> Story (Technical US)-->Task (any sub task type)

[Nic Brough -Adaptavist-]

Short answer then - no.

You cannot have Parent issue types as sub-tasks. All issue types have to be parent or child/sub-task and you can't use one as the other.

The structure you've posted looks like it's three levels as well. Jira only has parent and child/sub-task. You can't do anything about that.

However, the "Structure plugin" will let you get close to having many layers, see https://marketplace.atlassian.com/plugins/com.almworks.jira.structure

[Bala Krishna]

ahh this is the comment i got from the site.

Currently the plugin is not available for JIRA OnDemand :(

[Nic Brough -Adaptavist-]

The warning is telling you what is wrong - you need to make the "missing" issue types the same as the others that you can create.

Although, the way you've written the question makes me want to check one other thing - can you confirm that you have set up "story" as a type of sub-task and not a top level issue type?

[Bala Krishna]

Thansk for your help Nic. I haven't set up "Story" as sub-Task. I just want Standard Issue Types to come as Sub-task ,with out make it as sub-Task. we wanted to achive this structure.

+ Epic1 US (555)

+ Task1 (Design solution)

+ Functional US1 (New Forms)

+ Technical US1 (Creation of form - UI)

+ Task2 (adding UI fields)

+ Task3 (saving forms)

+ Task4 (updation of template)

+ Task5 (Unit Test)

- Test (Unit Test Case 1 – n)

+ Task6 (Functional Test)

+ Task7 (Update Design Document if any)

+ Technical US2 (Adding calculations if any)

+ Same tasks as above

+ Functional US2 (Update Forms)

+ Technical US1 (Modification of UI)

+ Task2 (adding UI fields)

+ Task3 (saving forms)

+ Task4 (updation of template)

+ Task5 (Unit Test)

- Test (Unit Test Case 1 – n)

+ Task6 (Functional Test)

+ Task7 (Update Design Document)

+ Technical US2 (Adding calculations if any)

+ Same tasks as above

+ Functional US3 ()

+ Functional US4 ()

+ Functional US5 ()

I am aware of creating EPIC and associating or dragging Story/Tasks to it. But i just want learn is there a way i can creat child userstory to a story or not in Jira