I wish to filter a Ticket View view a Single List Custom Field called "Product" but it is greyed out.
"Product is not applicable for the current project and/or issue type".
However it does appear in Request forms and tickets.
From your image, you have selected "Type": All. You should also check to ensure that your custom field is available for all issue types that you used in your project. I am suspecting that this field is not setup in the custom field context for all issue types for your project.
You should try to modified your filter by specifying the known issue types that have that field in the form and issues.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
Hi @Gavin Klose, although you mentioned the field appears in the forms and issues, have you checked the custom field context? Fields are typically grey out when not available for the project. Perhaps, the field context has been recently changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ivan Lima .
I fixed the issue via the custom field context but now the options do not appear in the filter?
Yet, options do work in the request form and appear in tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please share a screenshot of this custom field context? Also, to be on the safe side, is there only one custom field Product?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Ivan and @Joseph Chung Yin .
Here are some more screenshots of the Custom Field Contexts and Filter settings.
The set DropDown list options are not appearing in the Filter list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gavin Klose, I recreated the same scenario and ran into the same problem. It looks like we came across a known bug: JSDCLOUD-4737 - Basic search in JSD shows incorrect options when custom field restricted by project context.
I used the workaround described in the ticket above, and it worked for me. Basically, using the advanced search option. Something like:
issuetype in (Feature, "[System] Service request") AND resolution = Unresolved AND Product in (<your option 1>, <your option 2>, <etc...>)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.