Epic create a feature create a story

[Trena Norcia]

I need to have Epics have the option to create a feature and the feature have the option to create a story 

Like Task allows creation of a sub task

I currently have Stories as a base issue and need to know what happens when I convert to a subtask ?

So I am looking to have the Epic as the parent issue
as a parent the epic could have feature as a subtask 
I need the feature to have the story 

Epic ----------Feature----------Story  (in this order is this possible?)

Can someone help with this need?

[Trudy Claspill]

The built in issue hierarchy in Jira is

Epic > generic issues > Sub-tasks

...where generic issues are Story, Bug, Task, etc.

By default you can add additional issue types at the "generic issue" level, and you can add additional issues types at the Sub-tasks level, and the functionality for those new issue types will be the same as the other issue types at that level.

Jira Cloud Standard does not support extension of that hierarchy to include additional levels.

You could add Feature at the "generic issue" level, and use issue linking to establish a relationship between Feature issues and Story issues, but Jira would not automatically see that as a parent/child relationship.

There are several third party apps that can be added to your environment to help you extend the issue hierarchy. I have not used them, but some of the names I've seen include Structure and Big Picture.

Alternately, the Jira Cloud Premium plan includes a feature called Advanced Roadmaps, which allows you to extend the hierarchy from the Epic level upwards.

[Dave Rosenlund _Trundl_]

Hi, @Trena Norcia.  I'm afraid @Trudy Claspill is correct.

Of course, you can craft a marketplace search of your own, such as:

https://marketplace.atlassian.com/addons/app/jira/top-selling?hosting=cloud&query=hierarchy

or some variation thereof.

But in the end, Structure, BigPicture, and Advanced Roadmaps are the most frequently used ways of achieving what you describe. As you might suspect, each has its pros and cons.

You might also find this article, Epic-Feature-Story vs. Initiative-Epic-Story: Which SAFe Hierarchy Should You Choose? helpful (even if you are not using SAFe), no matter where you decide to go from here.

-dave 

P.S.  Full disclosure, I work for the company that makes Structure.

[Trena Norcia]

Thank you both so much!  This is great I am Jira cloud premium.  Will this effect my existing stories?   We were using the format Story>Task>Sub Task and are moving to epic>feature>story  

I need to understand how existing  stories will not be effected.

[Dave Rosenlund _Trundl_]

Being on Jira Cloud Premium you already have Atlassian Advanced Roadmaps -- I'd start there and see if you can do what you'd like to do.  The challenge you will face is, in Atlassian products the Epic - Story - Subtask is "sacred." 

Structure (and BigPicture) work with that sacred trio but also give you the flexibility to define any structure (hierarchy) you'd like.  With Structure, not sure about BP, you can even have different hierarchies for different teams.

Suggestion: Assess what will work well for you today but also think about what may come in the future.

Hope this helps,

-dave