To be able to create Features from Epics.

[koteswararao]

To be able to create Features from Epics. Create Stories from Features and create Tasks from Stories in Kanban board.

[Earl McCutcheon]

Hello,

In jira natively there is a set structure of the issue type hierarchy, Epic > Story > SubTask, and this cannot be rearranged by default and I will discuss the functional reasons for this below.  But, the add-on app Structure for Jira has a cloud and server version that does enable rearrangement of issue hierarchies if this is something you need to accomplish and I would recommend checking out the app to see if it fits your use case.

Natively in Jira, an epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories (which are standard issue types, some called stories as the issue type name). It may take several sprints to complete an epic and the standard issue types make up the sprints with the key takeaways. 

• There is no true difference between a Story issue type or a alternate standard issue types (Bug, feature, etc..), other than a semantic difference in the naming convention for internal use of that issue type and the Naming is used to implement Functional uses for the issue types and a story is default naming convention for the Agile grouping process and can be configured and connected to differing schemes such as workflows. but functionally they are all the same at this hierarchy level.
• Standard issue types are the layer above a Sub-task and below a Epic
• If you need to break certain Stories up into items that have to be assigned to different teams I would advise you to convert this Story into an Epic and make new Stories of the sub tasks, these Stories can then be assigned to different teams.
• Otherwise I would recommend using sub tasks underneath stories 

Additional details can be seen in: "Learn how to use Epics in Jira Software"

Regards,
Earl

[Jimmy Seddon]

Hi @koteswararao,

@Earl McCutcheon  is absolutely correct there are only three levels of hierarchy in which to create issue natively within Jira.  Can you explain a little bit more the use case for needing to go deeper than that?  From the backlog view you can filter epics to only display Stroies/Features and any Sub-Tasks that have already been created for the Stories/Features, then from the Kanban/Active Sprint view you are able to setup swimlanes based on the Stories/Features and that gives you visibility/filtering at the Story/Feature level.  I'm trying to understand the benefit of going deeper than that.

Any information you can provide would be helpful.

Thanks!

-James