JQL search by issueId fails if issue key LIST has a deleted issue

[Shailesh Shailesh]

I have a need where I need to get the list of issues remotely via their key. If one of the key corresponds to a deleted issues, entire JQL fails.

JQL: key in ("PROJ-1", "PROJ-5)

I also tried (with no luck)

key = "PROJ-1" or Key = "PROJ-5"
key in ("PROJ-1") OR key in ("PROJ-5")

I would expect that it should ignore the key that doesnt exist (like SQL). But in this case, entire JQL fails.

-Shailesh

[Neha Sharma · Accepted solution]

Too late to post a comment on the thread, but it can be helpful to someone. So here's my observation -

I faced the same issue while making JIRA API calls using JQL. Where it should have returned results for valid keys, but it returned an exception if any issueKey was invalid.

However, I noticed something strange. When we make the same JQL query and use lowercase for the keys, e.g "abc-1" instead of "ABC-1", it gives results instead of the exception.

[Leirbag Assuab]

Never too late to save the day to the others! Thanks for your workaround!

[Nikolai]

Thanks for the workaround! Better late than never. ;-)

[Mike Kessler]

you've got to be kidding me

great answer, thanks Neha!

[Kevin Coulson]

Works perfect, what a bizarre bug/feature! Thanks

[Zephyr QA]

convert  comma separated list  into lower case then it will work properly 

It will return non deleted key in result.

use like as below and try any one

JQL: key in ("proj-1", "proj-5")

JQL: key in (proj-1, proj-5)

I hope you will get answer.

[Sander Brienen [Avisi]]

How does the query fail? Does it give an exception, or just no results? I would also expect Jira to ignore the non-existing issue key.

This might be a bug in Jira. I would suggest that you file a issue at support.atlassian.com to check with Atlassian's support team.

[Shailesh Shailesh]

No Exception, It comes back with appropriate key not found message. I would except result containing all the found ones.

[Sander Brienen [Avisi]]

How does the query fail? Does it give an exception, or just no results? I would also expect Jira to ignore the non-existing issue key.

This might be a bug in Jira. I would suggest that you file a issue at support.atlassian.com to check with Atlassian's support team.