nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sorting User Stories under Features in Jira Roadmap

Phillip Nalesny

Dear Atlassian Community,

I'm encountering an issue with sorting User Stories under the corresponding Features in my Jira Roadmap. I'm trying to organize User Stories labeled with the acronym BKS-### under the Features labeled with CATART4-###. The User Stories are created at the team level, while the Features are at the ART level.

I tried 2 approaches:

1. when attempting to drag and drop the User Story under the respective Feature, it doesn't work.(see screenshot 1 "drad & drop") Drag & Drop.png

2. when using the Select & Bulk Actions function and clicking on Parent, I can't seem to select the specific Feature, which resides at the ART level, to nest the User Story underneath it. It says "no matches" (see screenshot 2 "select & bulk action parent") 2 select & bulk action parent.png

I've searched extensively for a solution, but I'm unable to find one. In summary, my question is: How can I nest User Stories under Features at the ART level in the Jira Roadmap?

Any guidance or assistance would be greatly appreciated.

Thank you in advance for your help!

Best regards, Phil

Accepted answers

All comments

Trudy P Claspill

Hello @Phillip Nalesny

Jira enforces the hierarchy of issue types globally. If your global issue type hierarchy is

Feature
|-- Epic
    |-- Story
        |-- sub-task

...then a Story's parent can only be an Epic. An Epic's parent can only be a feature. You can't skip intervening levels and set a Story's parent to be a Feature.

Does that match your scenario?

Phillip Nalesny

Hello @Trudy P Claspill

thank you very much for your answer. Yes, that matches my scenario.

Unfortunately we do not use Epics in our ART & Team. Is there any chance to adapt the hierarchy to:

Feature
|-- Story
|-- Sub-Task

Maybe that would be a solution.

Thank you very much for your support.

Ste Wright

Hi @Phillip Nalesny

You can customise the hierarchy.

Instructions are here:

^ It looks like you're on Server/DC based on the screenshots.

These instructions let you create the Issue Type and the Hierarchy, and then modify the "Epic" wording to make it "Feature" - eg. Epic Name > Feature Name, etc.

Ste

Phillip Nalesny

Hi @Ste Wright ,

thank you for your answer. I think I asked my question in a misleading way - sorry. I dont want to change the hierarchy of the issue types. In that case, I would get in serious trouble with the other 10 teams in our agile release train

Instead I would like to change the displayed hierarchy within the Jira road map to:

Feature
|-- Story
|---- Sub-Task

In a that way I would "ignore" the epics (because we dont use epics at all in our projects as an issue type).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software-cloud