Eg:
Epic, Sub-epic, Issue, Sub-tasks
Yeah - which structure.
Thanks for your reply Thomas. Basically we are looking at:
Epics -> Sub-epics -> Issues -> Sub-tasks
All with a 1-to-many relationship of course Can this structure be setup in Jira?
Thanks, Omar
Structure can set something up that looks a bit like multiple layers.
Portfolio can layer things above Epics
Thanks Nic. I'm surprised that Jira itself cannot do this!!
Most people really don't need it. I've run into several places that have implemented something to emulate it, and a lot of them have got themselves so knotted up in too many layers, they've lost all sight of what they're doing.
Hi Nic,
Thanks for your reply. As mentioned above we are looking at implementing just 4 layers (Epics -> Sub-epics -> Issues -> Sub-tasks) - epics (functional areas) and sub-epics (projects) for management reporting, issues to capture individual tickets of course and sub-tasks for IT to breakdown issues and assign time spent.
Do you think we can do this in a better way ?
Thanks, O
Hi Omar,
Both Portfolio and Structure can be used to achieve this.
Note that with Portfolio you'll have fixed levels, i.e. in the example above top level is always Theme, then Epic, then Stories and Sub-tasks. Each level above Story is assigned to a specific issue type. You can switch the UI to work on the specific level.
Structure allows flexible rules for building hierarchy, so you can arrange Epics hierarchically (so you can have a top-level Epic, a sub-Epic or sub-sub-Epic, without the need for additional issue types), and then attach Stories and Sub-tasks under their parent Epics.
Let me know if you'd like to see a live example.
Igor
Disclosure: I work for the company behind Structure.
Hi Igor,
Thank you for your reply. Could I setup a WebEx to discuss further?
Hi Omar, sure -- please write me at sereda@almworks.com and we'll schedule a call.
Kind regards,Igor
It looks like you're new here. Sign in or register to get started.