Advanced Searching with operator IN fails if value does not exist

Hi,

Considering the following scenario:

issue ACT-6 exists

issue ACT-7 does not exist

When, in the Advanced Searching panel, I use the following query:

issueKey IN (ACT-6, ACT-7)

I get the following error:

An issue with key 'ACT-7' does not exist for field 'issueKey'.

This seems to show that I can only search based on values that actually exist.

Also, when using the REST API to perform the same query, I get the following response:

HTTP Response Code: 400
HTTP Response Message: Bad Request
HTTP Response Body: {"errorMessages":["An issue with key 'ACT-7' does not exist for field 'issueKey'."],"errors":{}}

Is there a way to perform this query "a la" SQL ?

In other words, how can I search for issues using the issuekey field without having to worry if the key exists or not ?

Thanks,

Vasco

2 answers

0 votes

You can't do it now because JIRA explicitly does that error checking. You might want to raise a feature request to remove the restriction but to me it makes sense!

I've got a case where both issues ACT-6 and ACT-7 exists, but for a unknown reason, I have a message "An issue with key 'ACT-7' does not exist for field 'issueKey'." Any idea of what could be the cause ?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,115 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you