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

JXL Sheet Structure for Linked Items

Matt Riti

We use Jira Cloud Enterprise and I have a need to set up a Sheets Structure where Bug worktype items nest under the item under which they are linked via 'relates to'. Bugs and Stories are both at the same level (the level right below Epics). So out of the box the Bugs and Stories fall under the parent Epic. When I link the Bug to its related Story I need to have the sheet structure place the Bug under its linked Story in my Sheet hierarchy. Rovo claims this is possible but I am not able to get it to work. Does anyone have the correct levels' structure to use to get the Sheets to work as I have described.

Accepted answers

All comments

Jean Horn

👋 Hello @Matt Riti (Omnicom) !

Just so I have a better understanding before providing any information. 😁

Are you referring to setting up a spreadsheet structure to import data into Jira? Or would you like to export information from Jira organized in a specific way?

Marc -Devoteam-

Hi @Matt Riti (Omnicom)

Can you provide some more details on what you want, share some screenshots?
Are you referring to the List view in a space, work types of the same level can't appear in a stepped way, as they live on the same level

Otherwise you should reach out to the vendor of JXL sheets if this is possible, as you seem to use this 3rd party solution.

Maybe this part of their documentaiton gelps you further:

https://jxl.app/docs/guide/table-features/#custom-structure

Matt Riti

Hi Jean, No import or export of data. tThe JXL sheets add-on for Jira Cloud shows all jira items that are created for a space/project to show in a spreadsheet-like view within that space/project. There is a standard hierarchy that can be set up where the items cascade in the view by Epic → Story / Task / Bug → Sub-task. Bugs nest under Epics but I need them to nest under the Story for which they are linked in Jira. Jira allow for setting up custom structures other than what I indicated above. Thanks

Matt Riti

Thanks Marc. The page you posted is exactly what I am referring to so I will review and see if it helps answer my question. But from what you said it seems like the structure I need is not possible.

Jean Horn

@Matt Riti (Omnicom) sorry for the mistake! 😅

You might be basing it on Marc's answer!

I hope you find what you need! 😎

Alex John

I’ve been trying the same thing. The hierarchy usually only follows parent-child or epic links by default, so “relates to” doesn’t automatically nest the bug under the story. You have to set a custom level that looks at that specific link type. Did you already try adding a level for “relates to” under the story level?

Danut M _StonikByte_

Hi @Matt Riti (Omnicom),

It might be worth reaching out to the JXL support team directly for guidance.

If you're unable to achieve this with JXL, you could try the Work Breakdown Structure (WBS) gadget offered by our Great Gadgets app as an alternative. It allows you to display linked issues in the hierarchy you described.

Here is how to configure it:

on the Data tab:
- choose Visualization mode: Linked Work Items View
- choose a Data Source that returns your stories. For example, a JQL like this:

project = DEMO and issueType = Story

on the More Settings tab:
- choose to display only "relates to" link types

For more details, see also this article:

https://community.atlassian.com/forums/discussion/3150240/how-to-visualize-linked-issues-and-their-status-in-jira-dashboards

Hope this helps.

Danut.

Ivan Manolov _Appfire_

Hi @Matt Riti (Omnicom),

I'm on the JXL engineering team, and this is possible with a custom structure. As @Alex John pointed out, the trick is to give the Bug level a link-based parent relationship instead of the Parent field:

In your sheet, click Structures in the toolbar and choose Create structure.
Level 1: work type All epic work types.
Level 2: work types All base work types, parent relationship Parent field.
Level 3: work type Bug, for Parent relationships, then choose relates to.
Save.

Hierarchy built from work item links in JXL

If anything doesn't line up once it's enabled, let me know what you see and I'll take a look.

Best,
Ivan

Frédéric Tardieu_huminder_

Hi @Matt Riti (Omnicom),

I work for huminder, the company behind Board Studio app for Jira Cloud.

Ivan's JXL configuration is the direct solution if each Bug has one clear Story under which it should appear:

Epic level: all Epic work types
Base level: all base work types, using the Parent field
Bug level: Bug, using relates to as the parent relationship

One practical limitation of representing links as a hierarchy is that real relationships are not always one-to-one: a Story may have several related Bugs, and one Bug may relate to several Stories. A single nesting position can then hide part of the relationship graph.

An alternative is to keep Stories and Bugs at their native Jira level under the Epic and visualise every relates to relationship as an edge.

In this example, the Customer checkout Epic contains six Stories and six Bugs. Stories appear above Bugs, Priority provides the columns, and 11 many-to-many relationships are routed between the cards.

Capture d’écran 2026-09-25 à 21.42.51.png

Should you want to use a board like this one as an information radiator, there's an auto-update feature allowing real-time updates of the board. It's also possible to nest more fields horizontally or vertically, to add assignee, status and so on, without nesting limit:

Capture d’écran 2026-09-25 à 21.59.58.png

So I would recommend:

JXL’s custom structure when each Bug has one clear Story placement and you want a tree;
a graph view when preserving multiple Jira relationships is more important than assigning every Bug a single visual parent.

Cheers, Fred

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-cloud

structure