VersionSelectConfigure the VersionSelect field
Place the field on the right Jira layouts, set the picker limit, and understand how selections are stored and searched.
Add the field to Jira
For company-managed projects, add Service & Version to the applicable Create, Edit, and View screens. For team-managed projects, add the global field in the project's Fields settings and place it on the appropriate work type layout. Jira labels may vary by rollout. Requiredness is controlled in Jira.
Use the picker
Open the field editor, search for a service, then choose its version. Add further pairs, remove unwanted entries, or drag entries to reorder them. Save the work item to persist the selection. Canceling the edit does not archive a draft selection.
Maximum entries
Administrators set Selection rules → Maximum entries to an integer from 1 to 20; the default is 20. The setting applies across the installation and both catalog modes. Jira enforces a hard limit of 20 pairs.
A smaller app setting applies to the picker only; REST API and automation writes do not inherit it. Existing values over the current limit must be reduced before saving through the picker and are never silently truncated.
Search and saved snapshots
Versions initially show the most recent ten entries. Enter search text to find older versions and use Load more when available. Search always uses the current catalog.
Names and IDs are saved as snapshots. Renaming or removing a catalog entry does not rewrite existing Jira values. API service identity derives from group and name; changing either creates a new identity. Manual entries retain their IDs when renamed in the editor.
JQL examples
"Service & Version".serviceName = "payments-api"
"Service & Version".versionName = "2.4.1"The aliases serviceId and versionId also search actual saved IDs. Service and version aliases are separate arrays: combining conditions does not guarantee that both match the same pair in a multi-pair field.