Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Cannot edit a JQL query for SLA in JIRA service desk - Field value does not exist Edited

I've got an error in the JQL editor in SLA after I updated some field values in JIRA service desk. 

I am sure the field value in the syntax are correct.  But system shows the field value does not exist.

Is there anything I must do after the field value were updated? 



1 answer

0 votes

Make sure the name of the issue types for your project match the issue types in your JQL. The error is specifically saying that your project does not have a "Request access ERP or change security privileges" for the issue type and that the Urgency field does not have an option called "Critical - Business outage or significant customer impact".

Be sure both are spelled correctly and the case is correct. Also, try your JQL in a normal Issue Navigator to make sure that the query returns records.

Thanks for the reply. Actually I did not manually type the query. I used the JQL editor and let the system prompts the field value. I just don't understand why it still triggers an error. I assume whatever field value prompted automatically should be correct, and I do not necessary to change it.

When you manually create a new issue for that project, on the Jira side (not through the portal), is "Request access ERP or change security privileges" and option for issue type and is "Critical - Business outage or significant customer impact" an option for the Urgency field?

Just because the JQL Editor can find them, does not automatically mean that they are available for the project. The JQL Editor looks Jira wide so, the issue type and Urgency field option might not be on your project.

Actually the 'Issue type' were manually created. This was not an issue in the JQL editor for the SLA setup. The urgency field were originally come from JIRA service desk. But I modified the urgency field value. For example, 'Critical', I modified it to"Critical - Business outage or significant customer impact". The reason of this modification is to show the meaning of what 'Critical' means to the customers. I just feel for some reason, the JQL cannot take the modified field value although the JQL editor pull this field value automatically.

Latest update. I made a correction on the JQL. There is a green checkmark on the JQL editor. This shows my JQL is correct. But after I click 'update' in the SLA. This still prompt an error.


Did you manage to find a solution to this problem? 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

235 views 1 6
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you