I'm trying to Implement the following structure:
Epic > Feature > User Story > Sub-task
I'm not seeing where to add a feature level. Has anyone accomplished this?
We will have an Epic that has Reporting, UI, Performance and they are all a part of the EPIC but right now we are having to create multiple Epics and it's difficult to keep up. Ideally of we could have features underneath the Epic, it would bring a lot more structure/organization to our work.
Hi, LG. The simple answer is, no.
The more complicated answer it can be done but it should be done with a healthy measure of forethought (this article may help you think it through).
If you decide to proceed, you cannot get there with Jira Software out-of-the-box unless you already have (or upgrade to) a Cloud Premium or Cloud Enterprise subscription. They include Atlassian Advanced Roadmaps — which may or may not be the more expensive path for you.
You can also use Atlassian Marketplace products like Structure and BigPicture. Theycan help you get there, too, and are the most common marketplace choices for this sort of thing.
Hope this helps,
-dave
P.S. Full disclosure: I work for the company that makes Structure. Each of the choices above has its pros and cons / your mileage may vary, etc. :)
Hi @LG
Plugins mentioned by @Dave Rosenlund _Trundl_ may bring many other great features to support project planning & tracking.
In BigPicture, you can create a no-limited number of WBS levels, including Epic > Feature > User Story > Sub-task, based on links, and adjust it to your workflow precisely.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not off the shelf, it only does Issue -> Sub-task.
Jira Software adds Epics, so you can do Epic -> Issue -> sub-task.
Advanced Roadmaps allows you to add layers over Epic (Initiatives and themes for example)
Until very recently, that was it, the hierarchy was just those, and it wasn't codified.
You can also rename Epic to something else, but that looks a bit odd, because the UI won't change - you'll still have Epic reports, Epic name, Epic link etc.
However, soon, you will be able to rename Epic and have a codified hierarchy - see https://community.atlassian.com/t5/Jira-articles/Rename-epics-in-your-company-managed-projects/ba-p/1874726 - it should be rolled out across all Cloud sites by the end of March!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In most setups, I have seen Epic = Feature.
From your description would not Reporting, UI, Performance be components or labels? Epics are supposed to be delivered, and those don't seem like they will ever be closed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, most of us just live with Epic and use them as Features because of the renaming things. The UI elements are indeed components and labels, but they're all hard-coded.
Epics do get closed, when all their stories are complete.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.