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; } } }

Structure Config - Can't put Stories issues under Epic on Structure

unknown

I am using Jira Structure, having this hierarchy: Epics -> Story -> Tasks.

I would like links automatically created between these when I move them under another, or if I create them under another.

My goal hierarchy.

Epic
Story
Task

I created all my issues, with no links via the Structure interface - but the structure won't allow me to put Stories underneath Epics;

- When I add Task to a Story- I get this error:

"Issues cannot be added to non-epics. You were adding issue CHB-6 (TEMP)."

- When adding Story underneath an Epic:

"Cannot move issues inside JQL query result. You were moving issue CHB-2 (Load existing Resource tabl...)."

I used the generator preset of Agile Hierarchy

Please help

Accepted answers

unknown

Answer -

The problem is that I've inserted all the issues; and not just the epics; modifying the Insert query to:

project in ("CHB") and issuetype = Epic

Resolved the issue

All comments

Walter Buggenhout

Hi @[deleted]and welcome to the Community!

The agile hierarchy preset uses Jira's default issue hierarchy, which is:

Epics

> stories / tasks / bugs / ... (all standard issue types)

> sub-tasks

And so indeed, you cannot add tasks below a story. They are both on the same level.

If you want to create a structure where tasks really are at a level below stories, you'll need to apply a different approach using generators and extenders. To create a relationship between stories and tasks, you would also need to link them. Otherwise it is not possible to know which tasks belong to which stories.

Have a look at the documentation on how to use generators (you may want to use a JQL insert Generator to add epics to your structure) and extend generators (you will probably need an issues under epics extender to add stories and a linked items extender to add tasks under stories).

Hope this helps!

unknown

Thank you for your response.

To create the hierarchy I want, I followed the instructions provided by the previous response and used Jira Structure's Generators and Extenders.

But I still get the same errors every time I try to edit the issues on the Structure. My goal is to move the issues around in the structure and update the links between the tickets.

- When I try to add a Task to a Story, I get this error: "Issues cannot be added to non-epics. You were moving issue CHB-6."

- When I try to add a Story underneath an Epic, I get this error: "Cannot move issues inside JQL query result. You were moving issue CHB-5"

- When I try to add a Task underneath an Epic, I get this error: "Cannot move issues inside JQL query result. You were moving issue CHB-6"

Do you have any other suggestions on how I can create the hierarchy I want without encountering these errors? I appreciate any help you can provide.

unknown

Answer -

The problem is that I've inserted all the issues; and not just the epics; modifying the Insert query to:

project in ("CHB") and issuetype = Epic

Resolved the issue

Pieter Wouter Hartog

Did you ever find a solution for this? I'm having the same problems.

Stepan Kholodov

Hello @[deleted] & @Pieter Wouter Hartog

In the setup from the shared screenshots, it is indeed not possible to place an issue under another issue directly since all issues match the Insert generator's query. What you can do is the following:

1. Copy the issue you want to make a sub-issue.
2. Paste it under its new parent using keyboard shortcut: Cmnd+shift+V on Mac and Ctr+Shift+V on Windows. As a result the issue will be duplicated - it will still remain at the top level of the structure and it will appear as a sub-issue linked to its new parent.
3. Add a Filter generator to the structure with JQL query: issuelinktype != "link direction name" based on the link directon that appears in the sub-issue after it's linked to its new parent. And set the Filter to work on the first level of the structure. It should take care of the duplicate at the top level of the structure.

I hope this helps. If you need further assistance or have other questions about Structure, please reach out to us directly at our support portal and we'll get back with you shortly.

Best regards,
Stepan
Tempo (the Structure app vendor)

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

jira-software-cloud

structure