JQL for customer request type "no match"?

Charlie Misonne Community Champion Jan 26, 2017

Is there a way to query on the customer request type field being in the "no match" state?


When an agent changes the issue type of an issue the customer request type displays "no match". Unfortunately JIRA does not change the actual value to a matching type of the new issue type.


I added an automation rule triggered upon status change, comment and creation that will set the correct issue type.

I have to query like this: issuetype = Question AND ("Customer Request Type" is EMPTY or "Customer Request Type" != "question" )

If above rule is true the customer request type will be set to question in the automation task.


This works correctly. However it might be useful to be able to search for all issues without a matching customer request type. I'll create an improvement request if this is not possible yet.

3 answers

Charlie, my concern to what you wrote "I added an automation rule triggered upon status change, comment and creation that will set the correct issue type." is that when you CHANGE issue type it does not mean you change status (sometimes it's mapped to the same status within workflow for new issue type), not always you add comments as well as creating new issue is not an option when you are not making duplicate but want to change issue type in existing issue.

So my conclusion is that even though your automation makes sense, there is no relevant trigger what will make this solution work 100% for the situation when we simply change issue type of current issue :(

Charlie Misonne Community Champion Mar 21, 2018

Hi Thomasz

That's right, this solution is not ideal but that's the best I could come up with.

Any solution to this issue?

I did find that issues created in Jira are "EMPTY" and will display in issue searches as blank (even though looking at the Jira issues shows "No Match").   Those issues created in Service Desk show as "No Match" in the issue search which is different than EMPTY (which shows as blank).    These portal issues also show as "No Match" while looking at the actual Jira issue.

There has to be a way to identify these portal issues in a JQL Query search.  EMPTY does not pick them up.

0 votes
Jack Brickey Community Champion Jan 26, 2017


i must be misreading your question because it seems like you have already answered it w/in you automation?

what i think you are asking is how to query for all issues that have "no match" in the Customer Request Type.

if that is true the JQL would be project = xxx and "Customer Request Type" is EMPTY of something similar. No Match equates to empty.

I suspect maybe there is more to your question.

Charlie Misonne Community Champion Jan 26, 2017

Hi Jack

Indeed I resolved my own question. But while doing that I was wondering if a simple query exists to find all issues with a "no match" customer request type

Customer Request Type" is EMPTY is not similar to "no match". The actual value is kept and displayed as "no match"

Jack Brickey Community Champion Jan 26, 2017

When I use the filter i provided the list consists of issues which all have "no match" in the issue view screen as the CRT. Maybe there are instances of NM that are not being caught by this filter. I will need to look at this further.

Charlie Misonne Community Champion Jan 26, 2017

Probably because those issues were not created through the customer portal but with the regular JIRA create screen. At that moment the issue will only have an issue type and no customer request type. It displays "no match"

Try this:

  1. change issuetype of an issue that has a customer request type filled in
    ==> customer request types becomes "no match"
  2. Search for customer request type IS EMPTY
    ==> issue from step 1 is not in the results (in my case at least)

I'd be really interested to find an answer to this question; I am having the same issue.

I am having the very same issues in Jira 7.12.3 when an issue is moved between issue types.

In the issue list the old customer request type is shown:
(issue type = "Incident", customer request type = "Service Request")

Issue Navigator - Jira_2018-11-23_16-21-08.png

But in the issue itself it just shows "No match":

[SD-5484] 06_06_32.284-1 - Differenzen - Jira_2018-11-23_16-21-23.png


Jira 7.9.2 behaves slightly different by showing "No match" in the issue list:

Issue Navigator - Jira_2018-11-23_16-25-15.png


In both cases it is not possible to search for these issues except by creating an JQL containing all the incorrect combinations:

issuetype = "Incident" AND "Customer Request Type" = "Service Request"

But that gets very tedious very quickly when having several customer request types per issue type.

The corresponding bug JSDSERVER-5025 was closed as "duplicate" of JSDSERVER-3613 which does not mention this issue but is rather a feature enhancement...

Like 1 person likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 14, 2019 in Jira

Updates to jira.atlassian.com give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

719 views 1 15
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