Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JSM Next Gen | Normal for field Urgency does not not exist

Rodriguez, Jhon Ronald
Contributor
February 23, 2021

'Normal' for field 'Urgency' does not not exist

 

Jira screenshot.JPG

1 answer

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 23, 2021

That suggests there may be a hidden character in the "normal" name, or that urgency does not exist for this project.  When you enter the query, are you letting it do the type-ahead?  "Urgency = N" should prompt you with the "normal" value in whatever format Jira wants to put it in.

Rodriguez, Jhon Ronald
Contributor
February 23, 2021

thanks for your reply pal. here is the screenshot when i am entering the Normal.

jira ss.JPG

i just wonder why it giving me an option(Normal) that doesn't work at all.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 23, 2021

That is really odd, I assume that if you use the mouse to click on "Normal", it auto-completes the query in the search box?  And then tells you it is still wrong?  Do the other values work if you select one of them?

I have actually managed to replicate this by adding a non-printing character to the name "Normal"  (I.e. I renamed it to Nor¬mal but with the ¬ being an ascii break code - it shows Normal everywhere, but breaks the search lookup) but that's pretty obscure and you'd almost certainly have to do it deliberately - ascii codes have to be entered with key combinations or copying from other places)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events