customfield does not exist or you do not have permission to view it.

[Todd Thelin]

I am receiving this error message when doing an advanced search. I created the project, created the custom fields and this is the third of like ten that I cannot see. What did I do wrong in creating these fields? Is there a trick? I cannot remove the custom field because it is being used in 100's of issues already.

[Cody Stevens]

Hey @Todd Thelin 

I have seen a similar error when the field is apart of a context scheme. Did you add any of the fields to a context?

If you did, I noticed that I had to specify the exact project and I believe issue type when using the search to find issues with the field.

[Todd Thelin]

No I have not done that.

[Cody Stevens]

Okay, can you provide us with a screenshot of the error and the search you are trying to do?

[Todd Thelin]

I may have found a solution, it works but it is backwards from what I thought I was reading online. From what I read, you should use information gathered from the JSON screen when doing queries, but when I did that I received the error "customfield does not exist or you do not have permission to view it." I tried the same JQL script with the custom field's name and it worked fine. Is Atlassian going away from the JSON naming scheme or how would I know? It is really confusing to find out how to do something on their site that does not work. Should the customfield's names be the way I go then? Is this going to change again in the future?

[Richard Parkins]

Definitely use the name of the field that is mapped to the 'custom_xxx' field