Hi, I'm trying to create a time goal SLA and when I type in the JQL (issue type, incident AND Severity type =) and I choose any severity type from the preset drop down menu and hit save, I keep getting this error. 'The option 'sev-2' for field 'severity' does not exist. Even though it does exist and I chose it from the drop down..
Any idea what is going wrong?
So severity is a custom field I am assuming. Is it possible that you have two severity fields and maybe one of the fields has that option and the other does not?
what I suggest is this, JQL advanced search window and include the specific project you’re dealing with here and select the sev-2 option. What are the results?
Hi, Yes I believe it was a custom field I created. Although I checked the field list and there is only 1 'Severity' field and it has the description and preset dropdown I created. Also it must be selecting the correct Severity field as the JQL provided the drop correct drop down options.
What do you mean by JQL advanced search window? I'm quite new to JIRA..
In advanced search I typed this: project = "Incident Mgmt TEST AW" and "Severity[Dropdown]"
When I started typing 'sever..' the option [dropdown] popped up, I couldn't select sev-2 or any other of the severity rankings, only the [dropdown] was available. Have I not set up the custom field options correctly?
When I selected [dropdown] and hit search this is the error: Error in the JQL Query: Expecting operator before the end of the query. The valid operators are '=', '!=', '<', '>', '<=', '>=', '~', '!~', 'IN', 'NOT IN', 'IS' and 'IS NOT'
When in project settings > SLA > Time to resolution, I can use the following JQL to set for when 'Priority = medium' (another custom field I created or edited) and it works.
But when I try it on severity it doesn't work ("Ticket category" = Incidents AND Severity = Sev-2). The error message is 'The option 'Sev-2' for field 'Severity' does not exist. (even though it came from the dropdown while creating the JQL).
Assuming you are a jira admin do the following…
If you don’t see any values then you need to add them there and save it
I updated the drop down options for Severity from Sev-1 etc to Severity 1, as you see in the image above to see if that would help but it returned the same error.
Raised a bug and did a few screen shares with someone from Atlassian and we couldn't figure out the cause.
I've since deleted the field Severity completely and created a new one, and still having the same error message where I can't create the SLA based on the severity field options.
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
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