How to do: Vision -< Epic -< Feature -< Stories -< Acceptance Criteria in Jira

[Darren]

Hi,

I'm using Jira Service 7.8.2

I'm aware of the :

Projects -< Issues -< sub-tasks

and optional

Projects -< Epics -< Issues -< sub-tasks

hierarchies

I'm having a client that is sold on the following hierarchy and has asked me to research how this might be done in Jira.

Do you do this in Jira?  And if so, how did you implement it?

[Tomek-SoftwarePlant · Accepted solution]

Hi @Darren, 

Just wanted to correct the information @LarryBrock provided. You don't need BigPicture Enterprise for that. BigPicture Enterprise should be considered an add-on to the "regular" BigPicture that enhances it with several features. 

The standard BigPicture is enough if you want to create such a work breakdown structure. If you decide to give it a try, let me know - I'll be happy to show you how to do that.

Cheers. 

[LarryBrock]

Thanks for the clarification @Tomek-SoftwarePlant!

I wasn't where I could much research but I knew one of the SoftwarePlant products would do the trick.

Cheers,
Larry Brock

[LarryBrock · Accepted solution]

Hello @Darren,

While native Jira doesn't support the number of organizing layers you desire, there are add-ons that may let you do so and/or improve the flow through adoption of Scaled Agile practices.

Portfolio for Jira

BigPicture Enterprise

Structure

Hope this information helps and if so, please consider clicking the "Accept Answer" button so others benefit from he "answered" flag in their search results.

Cheers!
~~Larry Brock

[Thomas Deiler]

Dear @Darren,

with that many levels I recommend to evaluate the structure plugin.

So long

Thomas

[Vlad Lessage]

Hi Darren,

Thanks for posting!

I wanted to reinforce Thomas' suggestion about trying Structure for Jira if you're considering an app to accomplish your goals.

Structure helps Atlassian's largest customers visualize, track and manage progress across Jira projects and teams. It does this with adaptable, user-defined, issue hierarchies presented in a familiar spreadsheet-like view of Jira issues. In addition, structures may contain folders and other helpful organizational elements not found in Jira.

Please note that we offer evaluators a free, online, Structure Tips & Tricks session that is tuned to your specific use case(s). If you'd like to learn more about how Structure can help you, please reach out to our Support Team at support@almworks.com or you can email me directly at vlad@almworks.com.

I look forward to hearing from you.

Cheers,

Vlad

ALM Works

[Jack Hunter _HeroCoders_]

Hello @Darren

Here is one of the possible ways to get this kind of tree:

• Vision => Confluence page
• Epic => Jira Epic
• No idea why Features and Stories are separate levels, so it is hard to propose anything but let's try:
  • Feature => Jira issue (Story, Feature, etc.)
  • Story => Jira sub-task
• Acceptance Criteria => list of check items delivered by Issue Checklist app (provided by my team).

Personally, I would rethink the approach and flatten the tree by one level. 

I hope it helps.

Cheers,
Jack