Custom Field Filters
AdaptiveSurvey does not list every Jira field. + Add filter uses Jira field metadata available for the selected JSM space/project and work type/issue type.
Supported field types
Section titled “Supported field types”| Field type | Recommendation |
|---|---|
| Work type/issue type, priority, assignee | Built-in filters. |
| Single select, multi-select, checkbox, radio button, cascading select | Best custom field choices for chip filters. |
| User picker | Supported when the user values are available to Jira. |
| Long text, dates, numbers, Assets objects | Avoid for chip filters. |
| Portal-only fields or unlinked JSM form fields | Avoid because they are not the same as Jira fields. |
Make the field available
Section titled “Make the field available”- Create or choose a supported Jira custom field.
- Confirm the field context includes the target JSM space/project and work type/issue type.
- Add the field to the JSM work type/work item view.
- If customers should fill it in, add the Jira field to the request type request form.
- If you use JSM Forms, link the form field to a real Jira field.
- Refresh AdaptiveSurvey or switch away from and back to the project.
- Select + Add filter and search for the field name.
Check the field context
Section titled “Check the field context”- Go to Jira settings -> Work items -> Fields.
- Open the field contexts for the custom field.
- Confirm the context applies to the target JSM space/project.
- Confirm the context applies to the relevant work type/issue type, such as Incident, Service request, or Problem.
- Update the context if the project or work type/issue type is missing.
Add the field to JSM views
Section titled “Add the field to JSM views”- In the JSM space/project, go to Space settings -> Request management -> Work types.
- Select the relevant work type/issue type.
- Add the custom field to the work type fields or work item view.
This is the key step for AdaptiveSurvey filter discovery because the field must be available in Jira metadata for that project and work type/issue type.
Add the field to request types when needed
Section titled “Add the field to request types when needed”If customers should fill in the field:
- Go to Space settings -> Request management -> Request types.
- Select the request type.
- Add the Jira field to the Request form or Work item view.
- Save the request type.
If the field should be set automatically, use a hidden or preset value instead of asking the customer to fill it in.
Link JSM Forms to Jira fields
Section titled “Link JSM Forms to Jira fields”Plain JSM form fields are not the same as Jira fields. For filtering, reporting, JQL, and automation, link the form field to a real Jira field.
Missing-field checklist
Section titled “Missing-field checklist”| Check | What to confirm |
|---|---|
| Field type | The field is a supported finite or user field. |
| Field context | The context includes the JSM space/project and work type/issue type. |
| Work type view | The field is available on the work type/work item view. |
| Request type | Customer-filled fields are on the request form or work item view. |
| JSM Forms | Form fields are linked to Jira fields. |
| Options | Select fields have options configured. |
| Permissions | The user can access the project and field values in Jira. |
| Refresh | AdaptiveSurvey was refreshed after the Jira configuration changed. |