I use a Epic (MVP1/MVP2...) --> Feature (Use Cases) --> Sub-tasks

[Deleted user]

Hello

I am relatively new to JIRA....I use the hierarchy as  - Epic - > Features - > Sub-tasks. I am thinking - where do I use tasks here. And will the sub-tasks show up on my JIRA boards..

[Dave Rosenlund _Trundl_]

Hi, @[deleted].  This article touches on this topic, albeit from a SAFe perspective.  Nonetheless it's a short read and you may find it useful. Good luck with your decisions. 

-dave [ALM Works]   

[Addon Experts Center]

Hi,

In most cases, people creates a new issue type for the upper level (e.g. HL-Epic), rename the Epic to Feature.

It is common to use hierarchy type of add-on solution (e.g. structure, big-picture, panorama, etc) to see all the hierarchy and role-up statistics.

This will allow you use the most common scaled agile hierarchy:

HL-Epic

  Feature

    Story | Task | Bug

For feature planing you can use add-ons that allow you to plan on the Jira Epic level with sprints (addons such as Epic Timeline, etc).

I hope that this helps.

[Nic Brough -Adaptavist-]

DO NOT DO THIS.

You must not rename Epic in Jira Software.

By all means use Portfolio, Big-Picture, Structure, whatever, to create more layers, but do not rename Epic.  You will cause untold problems.

Atlassian are working on a way to change this, so it can be renamed without problems, as part of bringing it in line with Jira Align, but at present, no-one should rename Epics (or try to use them for anything other as a layer above Stories)

[Nic Brough -Adaptavist-]

With Jira Software, you have three levels of hierarchy, two of which are totally flexible on names.

In Jira-speak, you have Epic -> Issue -> Sub-task.

Epics are a single, one-off type - you can't have more than one issue type at this level and, at present, you should never rename Epic.

Issues though, you can call them anything you want and have different selections of them in different projects.  Most Agile people will recognise "Story" as a good type of issue, but you can add (or rename) any number of issue types you want at this level.  Feature is a perfectly good name here, as are Thing, Incident, Change, Help, Documentation, etc etc etc.  Have as many as you need (but try not to overload your humans with too many choices)

Sub-tasks - same as issues really when it comes to names.  But we see things like the explicit "sub task" and "technical task" representing part of a larger whole (the parent Issue/Story/Thing/whatever)

"Task", "Bug" and "Defect" are words that are a bit more fuzzy.  Some of us want tasks at an issue level, others at sub-task level.  Same for bug and defect (and with those two, I often see bug at the issue level representing something broken in released code, and defect at a sub-task level because it's failed a test before being released.  And sometimes vice-versa).  Those words, you should decide what fits you best!

[Deleted user]

Thanks Nic......this helps..considering that a Feature is only an Issue type......I think this is making sense to me. 

Adhoc actions will be created as tasks....else I will follow Epic - Feature - sub-tasks

Thanks