Is it possible to make new features issue type parents to stories and children of epics?

[Daniel_Gomes]

Trying to create a parental relation in which Epics are the top level, split into Features, and then features can be split into Stories. Same as works for Epics and Stories, but with a mid level being Features. Is it even possible?

[Antonio Dionisio]

For strict parent-child structure, you should create a new subtasks issue type named "Story" (as you can modify the default JSW Story issue type). Then in your project issue type scheme add Epics, Feature (Task type), Story (subtask).

Another option is to make it work using issue links.

[robert_turner]

I'm having the same problem.  I am trying to ensure my roadmap is showing Epics>Features>Stories.  All Stories should be the child of a feature.  This will enable a high level view of the roadmap to present to stakeholders.  I have an existing next-gen project that already has my existing backlog created.  At first we did not use features, only Epic>story.  This is not high level enough.  So most of the epics I created really should be features.  If I convert an epic to a feature, it breaks my links to the stories.  I was able to define this hierarchy in a regular Jira project, just not a next-gen.  Unsure why that's the case. 

If I use links, will those show up in the roadmap when I drill down under features to stories.  ANd in this case no story would have a parent.

[Johanna Malchow]

@robert_turner did you figure out a way to do this?