Recommended Free Tools
In Jira Cloud, a field context determines which spaces and work types use a custom field configuration. That configuration can set a default, provide a tailored list of choices, or filter users for a user-picker field. If a field has a different default or an empty choice list in one project, check the context that applies to that project and work type before changing the field itself.
What a field context controls
A context is a scoped configuration variant for a field. It lets administrators adjust how the same custom field behaves in different situations without creating duplicate fields. Depending on the field type, a context can set a default, define an alternate set of selectable options, or restrict which users appear in a picker. Values entered through different context variants still belong to the same field and can be used by reports that reference it. Atlassian explains field contexts.
As an Amazon Associate I earn from qualifying purchases.
Contexts do not all expose the same settings: what you can configure depends on the field type.
- Text fields: A context can set a default that populates the text box when a work item is created within that context’s scope.
- Fields with predefined choices: A context can have its own option list. That list is available only where the context applies. The option editor is case-insensitive.
- User-picker fields: Advanced settings can filter people by group or space role. Atlassian cautions that users with the global “Browse users and groups” permission may still see all user accounts.
A field with open-ended text does not have a selectable option list, so the options setting is not available for it. Defaults and choices are separate: changing a default does not add missing options to a select list. See Atlassian’s guide to advanced field options using contexts.
#1 Best Overall
How scope explains different behavior between projects
A context applies to selected work types and spaces. A global context applies in all spaces; a context that selects any work type can be used in team-managed spaces. If a field has more than one context, the applicable one determines which default, option list, or user filtering is used in that scope. A default configured for one project or work type therefore need not match the value used elsewhere.
To diagnose a difference, start with the exact work type and space where it occurs, then identify the context that covers both. Do not assume that a field’s contexts share identical defaults or choices. Atlassian’s current instructions for creating a context and defining where it is used describe the scope settings.
Inspect or change a field context
- Go to Settings → Work items → Fields.
- Find the target field, open More actions, and choose Contexts and default value.
- Review the existing contexts and find the one whose work types and spaces cover the affected work item. Add a context or edit one if the scope needs to change.
- Configure the setting supported by that field: a default for a text field, options for a field with predefined choices, or user filtering for a user-picker field.
- Save the change and check the field in the affected scope. If the field is used elsewhere, check those scopes too, since a context change may affect every work type and space it covers.
Choose a global context only when the same configuration should apply across all spaces; use narrower contexts when different scopes need different behavior. Labels and navigation may vary as Jira Cloud interfaces roll out changes, and available actions depend on permissions.
Why a select field has no available options
If a required select field shows no choices, confirm that the context applying to the affected work type and space actually contains options. Having values in another context is not enough if that other context does not cover the current scope. Atlassian’s empty allowed values troubleshooting guidance describes this situation and two remedies:
- Use a context that contains the needed values and applies to the affected scope.
- Add the required options to the context that is already active there.
Changing the default alone will not populate an empty option list. First establish that the correct context applies; then verify or add the choices in that context.
Contexts, field schemes, and screens solve different problems
A context controls what default or choices a field uses in a particular scope. It does not, by itself, determine whether the field is available or required, or where it appears in the work-item lifecycle.
- Field schemes: Govern whether fields are available or required for work types and spaces. Atlassian is progressively replacing field configurations and field configuration schemes with a unified field-scheme setting, so the labels and setup may differ between sites. See what field schemes control.
- Screens: Control where fields are shown during the work-item lifecycle, such as at creation or during a transition.
If a field is missing rather than merely showing the wrong default or choices, check its field configuration or scheme and whether the relevant screen presents it at that point. Atlassian’s field setup guide describes the “Find your field” function for checking configuration blockers.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Jira Cloud’s documented option limit
Atlassian’s Jira Cloud data-limits documentation states a maximum of 20,000 options per field, with enforcement beginning progressively from September 2026. Rollout timing can differ by site, so check the notices in your Jira interface for the limit’s status on your tenant. When the limit is reached, administrators cannot add another option, but existing options remain available. See Atlassian’s Jira Cloud data limits and guardrails.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
