The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

JQL - How to query issues that are linked between two projects and specific issue types

Kelvin Teng
April 18, 2024

Hi,

Need some assistance on how to we can query issues that are linked between two projects and specific issue types.

For example, we want to find issues that are linked between Project A and Project B and the issue types are Bug and Problem.

I am aware this may be achievable through plugins like ScriptRunner for Jira Cloud, but it is possible to use Jira's own native JQL? Because this query will be used in Backbone Issue Sync for Jira and I believe it only supports Jira's own native JQL, but please do correct me if I am wrong. 

Thank you in advance.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Trudy P Claspill
Community Champion
April 18, 2024

Hello @Kelvin Teng 

Your query cannot be achieved using only native Jira JQL capabilities.

You can find information about the native JQL capabilities here:

https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/

There is a function called linkedIssues() that enables you to search for issues linked to one specific issue with any or one specific link type. There is no function to find all the linked issues based on the project in which the issues exist.

0 votes
francis
Atlassian Partner
April 25, 2024

Hi @Kelvin Teng 

I'm Francis - part of the Exalate team, an app which provides similar functionalities like Backbone.

We get the same question and a workaround can be where you populate a custom field with the information you can use to build a standard JQL.

 

For instance - you could have a custom field 'Remote Key' containing the key of the issue on the other side.  The JQL would then be straightforward, selecting the issues where the remote key is filled in.

 

Hope this helps,

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events