Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Not able to select custom field in the filter - Field is not applicable for current project/or issue

I am trying to use the advanced filter to filter my defects but I am not able to select few customized field as its showing red exclamation mark that 

All Issue

Click on More on the right panel

Search the custom field

Try to click the checkbox


I am not able to select few custom field checkbox and its saying the below issue with RED exclamation mark

"Field is not applicable for current project / or issue type" 


Can anyone help in providing the exact steps to resolve this

3 answers

1 accepted

0 votes
Answer accepted

A field is "not applicable" when the context for the custom field does not place it on that project and issue type.

To make them applicable, go to Admin -> Issue -> Custom fields and go find the missing field.  You will see that in one of the columns towards the right, there is a context that specifies projects and/or issue types where the field belongs.  If you "configure" the field, you will be able to change that context, expanding it to cover the defects you're filtering on.

Thanks Nic for your reply. I do cross check the share setting and it was there but still we are getting the same error. Refer the attached snapshotCapture.PNG

Like Pavel Junek likes this

Thanks Nic its resolved now.

Ok, let's try this a different way.

Go to an issue in the Air Canada PSS project and edit it (with the edit button, not in-line), so that you have all the editable fields available.  There's no need to change anything for this, we just need to get to a function.

To the top right, there should be a configure button, usually used for showing and hiding fields for the current user's convenience, but there's another option on it called "where's my field?"  Use that, and ask it about "Reporter Group".  It will pop up a list of reasons why the field is not on the edit screen, with links for admins to fix them.  Some of the reasons on there also block fields from being available in search.

I have the same problem, the custom field is an Options Select field.  it's has Issue Types and applicable context associated yet not able to pick this field in Search.  Doing the "where's my field?" test, it is on the edit screen too.   however it's not possible to Search on this field??

Pavel Junek Community Leader Dec 05, 2019

Thank you guys! Description of the problem and its solution just helped me :-)

We also have the same problem.  Here is an example:


Field "Application Found In" is configured in Jira to apply to all projects, but only to the "Defect" issue type.

When using the Basic Issue Navigator interface, and selecting a project with the Defect issuetype and Defects in it with data in their "Application Found In" field, the field is greyed out and cannot be selected.  This is true even for querying on just a single project which only has the Defect issue type and no other issuetypes.  

This behavior could only be called a bug.

The only workaround is to change the configuration of the custom field so that it's context makes it apply to All issuetypes instead of being limited to just the only one in which it is used.  That's a very bad workaround because it completely defeats the purpose of having custom contexts at all.  But as far as I can tell, that's the only way to eliminate the error. 

The other option is to just use the Advanced interface, in which one would find that everything behaves exactly as it should. 

Same problem here.

This is still an issue within Jira Software. i can't believe it hasn't been addressed yet as it's existed for at least 2 years now.

I had the same issue as Andy Ukasick (thanks so much for posting) when trying to tie a specific Custom Field to a specific issue type. If one specifies this for a Custom Field within Contexts>Edit Configuration>Issue Types and uses anything other than Any Issue Type for Choose Applicable Issue Types than you will not be able to use that Custom Field within a Basic or Advanced filter. In my case, I was trying to include a Custom Field with Single or Multiple Choice Lists in a Filter but I was not able to pick a particular Custom Field Value as none of them would show up within the filter when tying it to only the Bug Issue Type. As Andy stated, this completely defeats the purpose of having Custom Contexts at all. I WASTED MANY MANY HOURS TRYING TO FIGURE THIS OUT AND TROUBLESHOOTING THIS!  PLEASE FIX!!!

Like # people like this

I can confirm this was the problem. Removing the project from the contexts gave back the ability to filter on the custom field appropriately.

I can still filter against the field using JQL or have ALL projects selected.

Hello from 2022! Does anyone reported this to Atlassian? Is there an issue in backlog for that?

Facing this issue now with 15k DC tier customer ... 

If the field is hidden in every field configuration, you cannot search for it. It needs to be shown in at least one project.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,130 views 34 44
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