Support "Stacked" / Linked Issue Expansion in JQL Results

[Singh_ Rahul_ENG_]

Title: Support "Stacked" / Linked Issue Expansion in JQL Results

Description:

Currently, JQL can only return a flat list of issues matching the query criteria. There is no way to query one issue type (e.g., Stories) and simultaneously retrieve their linked issues (e.g., linked Test Cases, Tasks, or Requirements) in the same result view.

Use Case:

As a test engineer working on a substation automation product, I need to:

• Query all User Stories in a sprint/release

• See their linked Test Cases, Requirements, and Tasks in the same view

• Verify traceability (Requirement → Story → Test Case → Bug) without manually opening each issue

Currently, I have to:

1. Run a query for Stories

2. Open each Story individually to check linked issues

3. Run separate queries for Test Cases, Requirements, etc.

4. Manually cross-reference them

This is extremely time-consuming for projects with hundreds of issues.

Expected Behavior:

Something like:

project = ABC AND issuetype = Story AND sprint = "Drop 4" EXPAND linkedIssues WHERE issuetype IN ("Test", "Task", "Requirement")

Or a "stacked" view that shows:

Story ABC-100 ├── Test: ABC-257 (linked) ├── Test: ABC-258 (linked) └── Requirement: ABC-50 (linked) Story ABC-101 ├── Task: ABC-300 (linked) └── Test: ABC-260 (linked)

Impact:

• Teams managing traceability (requirements ↔ stories ↔ tests ↔ bugs) spend significant time manually navigating links

• Regulated industries (energy, medical, automotive) require traceability matrices — this feature would make compliance audits far easier

• Would eliminate the need for external scripts or third-party add-ons to generate traceability reports

Workaround (current):

• Use issueFunction in linkedIssuesOf() (ScriptRunner only — not available in native JQL)

• Export to CSV and manually join linked issues

• Use Xray/Zephyr traceability reports (limited to test-specific links)

[Arkadiusz Wroblewski]

Hello @Singh_ Rahul_ENG_ 

There are existing Atlassian suggestions covering parts of this requirement:

JRACLOUD-21936  nested JQL function calls;
JRACLOUD-9197  nested or parent-child presentation in search results;
JRACLOUD-93962  richer linked-item information in the search list.

Best,

Arek🤠