nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Has there been changes to JQL operators?

Tobias H

Hello!

All of a sudden, my automations that are configured to respond to ""Request Type" = "<Type of Request>" has suddenly stopped working with the message:

The operator '=' is not supported by the 'Request Type' field.

The same automations ran perfectly fine and executed as intended on the last of June, but today all of the sort has the same error.

I've also tried using other operators to get it working, but to no avail.

Anyone that has any insight, or change notes to point to?

Update from Atlassian Support on cause of issue:

I investigated and was able to identify the issue causing the JQL to break. You are hitting a similar known bug:

Creating a custom field the same name with a system field breaks JQL that relies on the system field

To provide context, when there are custom fields (either global or team-managed) that have the same name as the system fields like "Request Type", it will break the JQL for the system "Request Type" field. This can only be replicated if the user executing the JQL has access to the project using the same custom field name.

Accepted answers

Nic Brough -Adaptavist-

One obscure thing to check.

Go to a search and blank out the current one, then start typing. Do not copy and paste, start typing Request Type. Jira will start trying to autocomplete after the first few letters, so when it gets down to fields starting with request, is there only one Request Type on offer?

All comments

John Funk

Hi Tobias,

I would open a support ticket to try to get to the bottom of it.

https://support.atlassian.com/contact/#/

Rilwan Ahmed

Hi @Tobias H ,

Go to menu --> Filters --> Advanced issue search.

Run the same JQL and see if it works. I tried an example JQL "Request Type" = "Get IT help (ITSM)" and it is displaying the results.

Also I added the automation rule and it did work without any issues.

Please check the rule audit log to see if someone had changed the rule.

Tobias H

Hi Rilwan!

I did try it in Advanced issue search and the error about = being the wrong operator appears there as well.

Here's an image of the "Validate query":

Screenshot 2023-07-03 120350.png

And here's the same in Advanced Issue search: Screenshot 2023-07-03 120434.png

Both of these screenshots were grabbed just now, so the issue still exists on my end 😓

Here's a screenshot of when it worked on Friday vs the failure today:

Screenshot 2023-07-03 120641.png

There hasn't been a config change on the rule since end of May, when I created the rule.

But if this issue is only on my end, I'll reach out to Atlassian support instead.

Thanks for the help! 😊

Tobias H

Yeah, it seems like that is the best way to go about it. Just wanted to check if I had missed any changes to the JQL language before that😅

Rilwan Ahmed

As @John Funk told earlier, its better you contact Atlassian support. I could not find anything related to Request type JQL operators in Change log

https://confluence.atlassian.com/cloud/blog

Nic Brough -Adaptavist-

One obscure thing to check.

Tobias H

Hi Nic!

I've already tested doing advance search completly fresh as well. There are a three fields to choose from, but the one that is tied to JSM is "Request Type - cf[10601]" Screenshot 2023-07-03 131054.png

Choosing it and adding a = starts listing the results of our actual request types.

Selecting one of them gives the green checkmark inside of the JQL field, but searching with any request type selected gives the error:

Screenshot 2023-07-03 131209.png

Have reported this to support already, so hopefully it will be resolved soon🤞

Nic Brough -Adaptavist-

I'd be strongly tempted to rename the other two. Just add a . to the end of the name or something.

John Funk

Ah! That's probably your problem then - you are probably getting crossed with the short text field which requires you to use ~ and not =

Try using the Customer Request Type field.

Tobias H

I'll look into it, I believe they were created by Developers who used to be admins before we tightened up the security of our Atlassian suite, and far before we purchased JSM.

Don't want to break anything for someone else while trying to fix our service desk automations 😆

But will try it if it seems safe 👍

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jql

automation

jira-service-management-cloud

jira-service-management