Skip to content
Kinline Docs

Custom Field Filters

AdaptiveSurvey shows custom fields in Add filter when Jira exposes them for the selected JSM project and work type, and when the field type can be used as a filter.

Supported fields

Section titled “Supported fields”

Select, multi-select, radio button, cascading select, checkbox, and user picker fields work best.

Select fields show available options. User fields use search.

Assets fields, long text, dates, numbers, portal-only fields, and unlinked JSM form fields are not good choices for Add filter.

Make a field available

Section titled “Make a field available”

Confirm the field context includes the target JSM project and the relevant work types, such as Incident, Service request, or Problem.

Add the field to the JSM work type or work item view. This is the key step because AdaptiveSurvey reads project field metadata from Jira.

If customers should fill in the field, add the Jira field to the request type request form. If you use JSM Forms, link the form field to a real Jira field.

After changing Jira field setup, refresh AdaptiveSurvey or switch away from and back to the project, then open Add filter and search for the field name.

Missing fields

Section titled “Missing fields”

If a field does not appear in Add filter, check that:

  • The field type is supported.
  • The field context includes the selected JSM project.
  • The field context includes the relevant work type.
  • The field is available on the work type or work item view.
  • Select fields have options.
  • JSM form fields are linked to Jira fields.
  • AdaptiveSurvey was refreshed after the Jira configuration changed.