Feature/Epic hierarchy

Tobias Söderlund

Hi,

Our team is investigating on how capture features and feature versions in JIRA and assing tasks to these.

The current approach is the following:

• Define a Epic as a feature version (Feature A v1 = Epic 1, Feature A v2 = Epic 2, Feature B v1 = Epic 3)
• Create tasks under that Epic (feature)
• Assign Epics (feature versions) to releases (Versions)

This way, we can track which feature versions going into different releases, keep our workflow etc.

So far so good, however.

We would like to have a to capture all feature versions under, let say, a master feature with the following hierarchy:

• Feature A
  • Feature A v1
    • Task 1,2,3
  • Feature A v2
    • Task 4,5,6
• Feature B
  • ...

This way we could capture design specs, manage features in a better way etc.

Now, we have of course experimented with the issue type feature, but that doesnt give us hierarchy when it just pops up as any other issue type.

The wish would be to have a column between "Version" and "Epics" where you could have "Features" and group the epics into differnet features.

If this is not possible, do any of you have any experience or ideas on how to work like this?

Thanks,

Tobias

Contact Kintosoft

IMHO, what you name feature (Feature A v1 = Epic) should be a Story (Feature A v1 = Story) rather than an Epic. Then, the "master feature" would be the Epic:

• Feature A (EPIC)
  • Feature A v1 (STORY)
    • Task 1,2,3
  • Feature A v2 (STORY)
    • Task 4,5,6
• Feature B (EPIC)
  • ...

Regarding:

Now, we have of course experimented with the issue type feature, but that doesnt give us hierarchy when it just pops up as any other issue type.

You could use JIRA regular links in order to make the hierarchy. Have you looked at the Links Hiearchy add-on? It may provide you a lot of flexibility and alternaives in order to find the best approach matching your needs as it brings to Agile all the power of JIRA regular links (issue hierarchies)