What JQL would return any dependent issue to issues in my project? (why: Advanced Roadmaps source)

[Erin Quick-Laughlin]

In Advanced Roadmaps, I'd like to add 2 data sources:

1. My project - which I can add by 'Project'

2. Issues from other projects, that either block an issue in my project, or will be blocked by issues in my project.

Constraints: 

A. I don't want to see any other issues from other projects in my Advanced Roadmaps, except my project issues, and the ones blocking or are blocked by.

B. I want to rely on only this issue link type of "Blocks", aka "is blocked by" / "blocks".   I do not want to specify labels or project names, because this is harder to scale across hundreds of projects & project leaders.  We would also have the benefit of automatically seeing a blocked/blocking issue in a project we didn't know about.

Steps taken to solve:

I believe the solution is in JQL's issueLinkType however we need to a way to include the issues that are in the Links field, without specifying outside projects in the JQL.

[Chris Buzon]

issueLinkType doesn't work in JQL queries on Jira Cloud. 

So you won't be able to build a single filter to expose the tickets you want based on Link Type. I've only been able to use Structure (the addon) to actually do something specific with custom link types.

Others here may have ideas to help, but I've had to resort to using labels/custom fields and jira automation to do what you need.

[Erin Quick-Laughlin]

For clarity, I'm thinking of using issueLinkType starting with something like this, which seems to work for our cloud instance...  

But it's the results of that field that it would be great to have access to, to pull in.

I'll check out Structure.  It's also been a little while since I posted this, and wonder if JQL Extended Search app might help (which we now have)