Work breakdown structure and Issue Type in JIRA

Question

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?

Ateef · Answer

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,

Ateef · Answer

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.

Joshwa Marcalle · Answer

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