4 answers
Hi @Trinath.Putchala ,
If you're on Premium plan, you can configure issue type hierarchy and add custom hierarchy levels.
However, as official docs state, changes to the hierarchy will apply to all company-managed projects.
Potentially, you could set Feature issue type on the same level as the Epic and then create custom Epic issue type and set it above. Then you can configure issue type scheme for that specific project so it only contains Feature and custom Epic and you'll probably get what you'd like.
But, again, this would impact all company-managed projects so whenever someone else uses Feature or custom Epic within their projects, the same hierarchy will be applied.
Note that with the existing approach, if all other projects use Epic - Story - Sub-task hierarchy, this configuration will remain.
Cheers,
Tobi
welcome to the community!
as already mentioned,
- If you have Jira Premium, you can add additional hierarchy levels, however always only on top of epics, and
- Jira's hierarchy configuration is global for your site, meaning that you can always only have one.
The only thing I can think of is to use issue links to model your project hierarchy. An issue link can connect any issue with any other issue, so you have complete freedom. The downside is that Jira doesn't really recognise an issue link as a parent/child relationship, and therefore won't give you a lot of hierarchy-related features.
There are, however, a number of hierarchy-focused apps on the Atlassian Marketplace that can help with this. E.g., my team and I work on an app in which your use case should be easy to solve: JXL for Jira.
JXL is a full-fledged spreadsheet/table view that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of advanced features, including the support for configurable issue hierarchies. These issue hierarchies (a.k.a. structures) can be based on Jira's built-in parent/child relationships (like epic/story, or task/sub-task), and/or based on issue links of configurable issue link types (like is parent of / is child of).
E.g., this is an example of a hierarchy similar to the one you're looking for:
In this example, epics, features, and stories are connected via issue links. Note that this hierarchy wouldn't be global by any means, but really only be visible in this specific JXL sheet.
Any questions just let me know,
Best,
Hannes
Welcome to the community !!
As suggested by everyone a mktplace app can help to create a custom hierarchy using issue links. If you would be interested to try out one, take a look at
The app allows you to create a hierarchy using issue links. You can link any issue type above or below epics / stories / tasks or in fact at any level. The app shows %complete progress at each parent level. It roll ups the time tracking fields, story point or numeric fields at each parent level.
Disclaimer : I am part of the app team
Hi @Trinath.Putchala ,
You can achieve that with Marketplace app for linked issues. E.g. Pivot Report (we are developers) supports custom hierarchies per saved report. Therefore, it's not affecting other projects:
In this demo report we use custom issue types and "is blocked by" link to get Theme > Initiative > Epic > Task > Sub-task hierarchy.
You can check on our own: custom hierarchy demo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.