Quick Fix Summary
Try linkedIssues(issueKey, linkType) in JQL to grab issues tied to yours via a specific link type. Swap in your issue key (like PROJ-123) and the exact link type name (say, blocks). Fire it off in Jira’s search bar or Issue Navigator—no admin rights required.
What’s going on here?
You want to list every issue linked to a certain Jira ticket with a specific relationship—think “blocks,” “relates to,” or “duplicates.” Jira hides these in the regular UI, so you’ll need JQL (Jira Query Language). The built-in linkedIssues() function lets you filter by link type, which is perfect for audits, mapping dependencies, or sprint prep.
(Case matters—link types are picky. If your setup calls it “Blocks” with a capital B, you have to use “Blocks,” not “blocks.”)
Let’s fix this step by step
1. Fire up JQL search
- Head to your Jira project.
- Up top, pick Issues → Search for issues.
- If you’re stuck in Basic view, click JQL to jump into advanced mode.
2. Type in the linkedIssues function
Plug this straight into the JQL bar:
linkedIssues("PROJ-456", "blocks")
Just swap PROJ-456 for your real issue key (say, DEV-101) and blocks for whatever link type you need (like relates to).
3. Run the search
- Hit Enter or click the search icon.
- You’ll see only issues linked to PROJ-456 with the “blocks” relationship.
4. Peek at link types (optional)
Not sure which link types your Jira knows?
- Head to Project Settings → Issue Linking.
- All the link types live under “Link Types.”
Still not working?
1. Double-check spelling and capitalization
Jira link types are case-sensitive. Grab the exact spelling from Project Settings → Issue Linking. If it’s “Is blocked by,” use that whole phrase—not “Blocked by.”
2. Wrap it in full JQL syntax
Some older setups need the function tucked inside a proper clause:
issueFunction in linkedIssues("PROJ-456", "blocks")
That keeps things compatible with older Jira versions or custom tweaks.
3. Try a subquery in Advanced Search
Need to find issues that link to a whole batch of issues?
- Open JQL search.
- Drop in:
issueFunction in linkedIssues("PROJ-456", "blocks") ORDER BY created DESC
That returns every issue linked to PROJ-456 with “blocks,” newest first.
How to keep this from happening again
1. Keep a cheat sheet of link types
Jot down all the link types your team uses in a shared spot (Confluence works). Spell them out exactly, note the capitalization, and add quick usage notes. That stops typos and makes your queries easy to reuse.
2. Save handy JQL queries as filters
Turn your go-to linkedIssues() queries into reusable filters:
- Run the query.
- Click Save as in the top-right.
- Name it something like “Blocked-by Dependencies - PROJ-456” and share it with the team.
3. Do a quick link-type audit every few months
As of 2026, Jira Cloud admins can run an audit under Jira Administration → Issues → Issue Linking. Toss out any link types you’re not using—fewer types means cleaner queries and faster searches.
According to Atlassian Support, unused link types can drag down JQL speed and throw off results.
