Next-Gen Project Filtering Issues by Custom Fields

Question

I created a Next-Gen project, created a custom field, and when I try to filter a List View by that field, it tells me that the field is invalid for the project or issue type.  My custom field was added via the Project and added to every issue type.  What am I missing?

Also, is there a way to filter Backlog by something other than the Epic (custom field, for example)?

Alexander Developer · Answer

I have the same problem. I use Jira Cloud. My project has next-gen type.

I have created a custom field. The automation rule makes a timestamp at this custom field when a task moves to a certain Status. When I try to select sorting advanced filter by this created custom field, I get the message this custom field isn't applicable for this project or issue type.

I checked, this custom field is in Global scope and exists for all issue types. I tried to select any type of custom field - the result was the same).

What thing could be the reason for this unsuccess?

David Oldroyd_2whltp · Answer

I have tried this workaround and the error that I get on the advanced search screen is "The operator '=' is not supported by the 'External ID' field." The field I created is a text field so I'm not sure where to go from here.

Thanks in advance for any suggestions.

michael.walton · Answer

Thanks @Kevin Bui.  That is the issue I was having, and I did see that I could use the Advanced query to get what I want.  I think what was bothering me is that even in the List View, selecting just my next-gen project as a filter didn't allow the Basic to work properly.  In older versions of JIRA, as long as the other filters got you to a place where a custom field was being used, you'd be able to use that custom field to filter in a Basic query.  It's just a change in behavior from what I've seen from JIRA in the past (10+ year user, btw).