Is there a way to setup JIRA issue hierarchy to allow Stories to be Parents of other Stories?

[John Chen]

Currently, the Stories that are created by Product requires multiple platform teams to implement.  Each of the platform teams (i.e. Mobile, Server, Infrastructure) will create their own Stories relevant to the development effort.  The development stories are linked to Product story with dependency linking, but there's no way currently to link them to the Product Story as Child stories.

[Joe Pitt · Accepted solution]

No. There may be a plugin that allows a setup that mimics what you're looking for.  Is there a reason you don't want to use an Epic for the top level?

[John Chen]

That would mean to move Product user stories to Epic. It will need some socializing and convincing.

[John Chen]

Also, if we do move the product stories one level up, that would also require another level above Epic.  Assuming we can the following, will JIRA allow such a hierarchy?

Initiative -> Feature -> Epic -> Stories

[Joe Pitt]

You can create a new issue type of Feature and then LINK they epic to it. There is a plugin that may do that. I believe it is called Structure

[Dave Rosenlund]

@John Chen: @Joe Pitt is right.

Structure for Jira is one of a handful of apps that lets you organize your Jira issues into any (existing or new) hierarchical scheme you wish. For many companies, it's the way they were able to adapt Jira to the way they were (or want to) manage projects without having to follow a prescribed hierarchy.

Check it out. And if you have any questions, you can reach us via structure@almworks.com.

-dave [ALM Works - the makers of Strucure]