Jira Product Discovery: Reuse global fields
Reuse a Jira Product Discovery global field through Space settings → Fields → Add global field, selecting the existing shared definition.
A Jira admin creates and edits global fields centrally. Use a shared Customer segment field across product spaces when its names and options should have the same meaning everywhere.
Step-by-step guide
Choose whether the field should be global
Agree on the shared vocabulary before creating it. For example, a Customer segment field may need the same options across Payments and Onboarding, while a team-specific experiment code can remain local. Ask a Jira admin to check for an existing suitable global field.
Add the global field to the space
Open the space’s More options → Space Settings → Fields and select Add global field. Search All, Discovery or Jira as appropriate, inspect the field details and select Add. Then enable the field in the relevant view through Fields.
Migrate existing values carefully
If replacing a local field, a space admin can choose Migrate field values to a global field. Select fields of the same type, review and map their options if prompted, then Migrate values. Check representative ideas before replacing the local field in every view.
Coordinate future changes centrally
Global names, options and other properties are shared. Consult affected space owners before a Jira admin changes them. Formula fields require migrating their dependencies and recreating the formula; they cannot use the ordinary stored-value migration path.
Common mistakes
Deleting the local field before checking the migration
Inspect populated global values and dependent views first. Deleting a field can lose the remaining local data.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.