Next-Gen Project Filtering Issues by Custom Fields

[michael.walton]

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]

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?

[michael.walton]

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).

[Kevin Bui]

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

Aside from the text search and assignee filter, you can also filter by Label but I believe this option only displays if there are issues in the Backlog with labels.

[Kevin Bui]

Hi @michael.walton - Is this the error that you're getting?

 {fieldname} is not applicable for the current project and/or issue type

If so, I think the problem is that the list view that you're on is for all projects, and your custom fields are only for your next-gen project.

If this was a normal custom field on a classic project, you could change the field configuration at Jira settings > Issues > Custom fields. However, because next-gen configurations are scoped only to that one project, this isn't possible.

You could use advanced searching/JQL as a workaround. An example query would be something like this:

project = "My next-gen project" AND "My custom field" != empty ORDER BY "My custom field" ASC

Where My next-gen project is your project's name, and My custom field is the name of your field.

[David Oldroyd]

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.