Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

The operator 'is' is not supported by the 'linkedIssue' field.

trying to do this JQL (which was working before):

created >= 2023-06-01 AND created <= 2023-12-31 AND project in (TA20, BC526, SOTF, OM, COR, CE, CMTP, HEL, HP, SW, WMS) AND issuetype = Bug and linkedIssue is EMPTY

 

but now is not working anymore and I am getting this error:

The operator 'is' is not supported by the 'linkedIssue' field.

 

Anyone else encountered this? Please share how to resolve or an alternative. I am trying to search for all bugs that have no linked issues. 

2 answers

2 accepted

1 vote
Answer accepted
Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 16, 2023

Hi @Princess Dagala 

As @Tim Kopperud mentioned this option is bit available, see referenced Atlassian documentation that he mentioned.

Try:

created >= 2023-06-01 AND created <= 2023-12-31 AND project in (TA20, BC526, SOTF, OM, COR, CE, CMTP, HEL, HP, SW, WMS) AND issuetype = Bug and linkedIssueType is EMPTY

0 votes
Answer accepted
Tim Kopperud
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 16, 2023 • edited

Hi @Princess Dagala

LinkedIssue cannot use IS operator. it need to be the = or != operators. See this document about supported operators for linkedIssue JQL functions | Jira Software Cloud | Atlassian Support

Try this:

created >= 2023-06-01 AND created <= 2023-12-31 AND project in ("IT Support") AND issuetype = Bug and issueLinkType is EMPTY

TimK. 

Thanks Tim. But I am not using the issueLinkType

I am searching for Issues (bugs, test cases) that have no linkedIssues

Tim Kopperud
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 16, 2023

Hi @Princess Dagala

issueLinkedType IS EMPTY will return all issues that doesn't have an issueLinkedType related, which are all issues without any links to other issues e.g., no linked issues (hence not used).

Did you try the JQL I attached? Please let me know if you get non-expected issues returned from that JQL. 

TimK.

Like Bill Sheboy likes this

Thanks Tim, I am able to create the JQL. Thanks for your help!

After some time, (after saving the filter) the query is erroring out saying: An unknown error occurred while trying to perform a search. 

 

The chart for this in the dashboard returns and error: 

Rate Limit Reached

Jira was contacted multiple times but kept saying that it was too busy to handle this request right now. Please reload the page to try again.

 

screenshots below:

 


IssueLinkType - JQL.JPGIssueLinkType - Dashboard Chart.JPG

Tim Kopperud
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 18, 2023

Hi @Princess Dagala, this can be a temporary glitch. You might retry at a later time. 

If it doesn't go away you can try playing around with the JQL to shorten the result list.  E.g. by only requesting one project. Just to see if this solves the problem. 

TimK

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events