Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

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.

1 answer

0 votes

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.

No I have not done that.

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

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?

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

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