Forums

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

Cannot specify Filter for Custom Field in Basic Search despite configuring correct Contexts

Alistair Edge September 18, 2019 edited

When using the basic search in Jira to specify a filter from the custom field "Severity" it is greyed out, with the red exclamation warning beside it stating:

Severity is not applicable for the current project and/or issue type

...despite:

  1. Configuring the custom field context to apply to the correct Project and Issue Type
  2. When searching, only filtering for the very same Project and Issue Type

Oddly enough I can still:

  1. Get successful search results using JQL without specifying Project or Issue Type:
    1. JQL: severity = "Severity 1"
  2. Returned issues from other searches still have their "Severity" column populated

...so I know the data is there, Basic Search just won't hand it to me.

I can get it to work when I remove specific Issue Types and instead have the Custom Field apply to all of them. So is something wrong or is this intended behaviour?


I also noticed a field (In yellow) is not populating with Issue Types on the Configure Custom Field: Default Configuration Scheme page when I've selected specific ones:

Blank Issue Types.png

What's my outcome? To only have certain fields for specific Issue Types as they don't apply to all of them in the Project. As some fields are "Required" it can be frustrating to be "Required" to enter a field when the Issue Type may be irrelevant.

Any help is much appreciated, I've been at this one for a while!

1 answer

0 votes
Alistair Edge September 25, 2019 edited

Still not fixed.

Suggest an answer

Log in or Sign up to answer