We are trying to configure a new hierarchy level in Advanced Roadmaps (JIRA DOT), but facing several

[Kateryna Helrod]

We work in JIRA DOT

Hierarchy Levels - Advanced Roadmaps - Jira

We are trying to configure a new hierarchy level in Advanced Roadmaps (JIRA DOT), but facing several issues:

1. We are unable to configure new hierarchy levels (see items 1, 2, 3).

2. Existing hierarchy levels (those without numbers) appear to be not editable — for example, we cannot deselect "Epic".

3. It is not possible to associate the issue type Feature with the hierarchy configuration.

Goal:
We want to introduce an additional hierarchy level — Feature — between Epic and Story.

Request:
Could you please assist with the configuration? Specifically:

• Which actions are required to add or configure hierarchy levels?
• Is this behavior expected, or are we facing a misconfiguration?

Internal Analysis:
Our internal JIRA DOT support provided the following statement:

"Unfortunately, your issue is related to a plugin (even though it is now part of Jira, it was previously a paid plugin), namely Advanced Roadmaps for Jira.
We are not familiar with the plugin in detail and cannot identify the issue.
We recommend contacting Atlassian Support directly.

Also, after checking other Jira instances, we observed the same behavior. It seems to be a default configuration, and further guidance is needed to understand how to achieve the desired setup."

[Duc Thang TRAN]

Hello @Kateryna Helrod 

I can't see your screenshot, but based on your description, it seems like you need your instance to include Feature as an issue type at level 2 — which means it's above Epic in the hierarchy.
To achieve this, admin product need create this new issue type and defin in hierachie issue then their  need to add this issue type to your project.

https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

Once that's done, you should be able to see it in your Advanced Roadmaps plan.

You can filter by issue level.

If you prefer not to see any Epics, you can modify the plan source to exclude them.

Hope this can help . 

[Kateryna Helrod]

Hello @Duc Thang TRAN

Thanks for your reply!

The Feature issue type is already created and configured in the hierarchy in Advanced Roadmaps at level 2 (second position). However, it doesn't seem to affect the default hierarchy (Epic → Story → Subtask). We’re still unable to create links between Epic and Feature, or between Feature and Story.

Thanks any way!

[Duc Thang TRAN]

@Kateryna Helrod 

 I don't understand. If Level 2 it means that Feature is higher than Epic 

If Feature is Level 2, then normally the hierarchy should be:
Feature (level 2) → Epic  (level 1) → Standard issue  (level 0) → Sub-task (level -1)

Normal you can create a link  between Epic and Feature . Parent field  on Epic  (with the feature issue key) . Not for Feature and Story

Why is Feature in the second position? Do you have a screenshot to show this?

Also, this issue type needs to be added to your project's issue type scheme. Make sure this issue type is allowed in your source for Advanced Roadmaps.

You can do something unusual, like making Epic Level 2 and Feature Level 1. In that case, the hierarchy could be:
Epic → Feature → Standard issue → Sub-task

But keep in mind: this hierarchy applies across the entire Jira instance, not just your project and will have a lot change to project . Personally, I'm not a fan of that approach

Alternatively, you can install a paid plugin like Structure if you want to create a personalized hierarchy structure.

Best,

Duc Thang TRAN

[Dick]

Hi @Kateryna Helrod Welcome to the Atlassian Community,

Your main goal cannot be realized in Jira. Even in the Cloud version, where issue hierarchy can be changed you are not allowed to put an issue type in-between Epic and Story (I tested this).

As an alternative, you can have an issue type above epic, ie initiative. That would give you ample hierarchy to account for the different layers in your organization. 

Kind regards,
Dick

[Kateryna Helrod]

Hi Dick,

Thanks for the welcome words and your prompt feedback .

We do need the hierarchy in the sequence Epic → Feature → Story — it's a bit unfortunate that Jira doesn't support this setup.

Thanks anyway for the suggested solution.

[Dick]

Hi @Kateryna Helrod

I often feel people (in general) care too much for semantics. As long as something works for a team, it's more than okay to be different from the rest. 

Kind regards,
Dick