Work breakdown structure and Issue Type in JIRA

[Ateef]

I'm having trouble with a process that is currently breaks down a uses a user story into smaller user stories e.g.

• Epic
•     User Story 
•        Story Feature 1 (linked to User Story)
•        Story Feature 2 (linked to user Story)

Can someone help me with potential issues I can run into with this Issue type hierarchy?

[Joshwa Marcalle]

Hi Ateef,

You can do this by creating custom Subtasks and then adding them to your issue type screen scheme and workflows. No need for an addon for this at all

[Ateef]

Thank you for the response Joshwa

I'm aware of the add-on and sub-task route, wondering what are the pitfalls of linking user stories to smaller user stories?

Does it impact reporting, burndowns?

Not a best practice to link stories etc.

[Dave Rosenlund _Trundl_]

Hi, @Ateef.  You could consider using Jira sub-tasks for your story features.

Beyond that, there is no easy way to do what you are describing with Jira out of the box. However, there are a number of Jira apps on the Atlassian Marketplace that add this functionality to Jira. They effectively give you the ability to craft your own/arbitrary hierarchies to suit your needs. 

One such app is from the company I work for, ALM Works, and it's called Structure for Jira. You may also want to look at BigPicture from SoftwarePlant.

-dave [ALM Works]

[Ateef]

Hi Dave 

Thanks for the response.

Checked out the add-on and it does help, I'm actually  looking for a response that will either tell me if this is a best practice or recommend a better way to leverage the existing JIRA framework,