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

Your Points Tracker
  • 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
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?
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

Custom Field not a JQL Filter Option

I have created a custom field called "Deploy To". This field has been in use for years, and renders correctly on issues.

When trying to use this field in a basic or JQL query, the field will not show up.


The most common resolutions for this issue involve tweaking the field's context, as its usually restricted to specific projects or issue types and the user needs to add this criteria into their query to gain access to their custom field. This is not the case for me.

The only (and default) context i have for my custom field is for "any issue type" and "Global context" (all projects). So the permissions are as open as they can possibly be.




Example of a basic query (Deploy To custom field is missing..)



Example of a JQL query (Deploy To custom field is missing...)


1 answer

1 accepted

1 vote
Answer accepted

Could you check what the searcher for the field is?

Go to Admin -> Issues -> Custom fields and find your field, then use "edit details" from the drop-down menu on the right.  You should see Field name, description and search template - what is that last one saying?

Ah, one place i had not looked. It was using Search Template "None". I've updated it to use "Multi Select Searcher", and its working just fine now.

Thanks Nic!

Fantastic!  It was a bit of a guess, because we hadn't looked at it before.  I was hoping it was that as it's an easy change but wasn't prepared to assume it would be that.

There is one more thing with it though - without a searcher, the field does not know what to write into the index and hence, has not.  So although it now looks searchable, existing data is not yet indexed.  Issues that are created or edited since you changed the searcher will become indexed and hence fully searchable, but untouched ones will not.

At some point, it would be worth running a full re-index across your system to get the old untouched issues up to date.  You don't need the fully locking indexing, just the background one (it may make things slow for the users, so do it out-of-hours)

Gotcha. I really appreciate your thoroughness Nic.

I'll run the re-index tonight and get everything up to date.


I had the same issue, Nic's solution work for me :)

Thank you very much!

Suggest an answer

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

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

283 views 16 17
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