ThisCalculator

Everyday

Jira Cloud Field Contexts: Defaults & Options

Updated · Standard formula, shown below

Field contexts in Jira Cloud control which projects and issue types a custom field applies to, and they let you set different default values and available options for the same field in different situations. This guide explains how contexts affect those settings and walks you through configuring them correctly.

What You’ll Need

  • Jira Cloud admin access (Jira administrators or Global administrators permission).
  • A custom field already created (you can create one during the steps if needed).
  • Understanding of your project and issue type structure.

Step-by-Step

  1. Navigate to the field configuration. Go to Administration (gear icon) > Issues > Fields. Find your custom field in the list. Click the three-dot menu (⋯) next to it and select Contexts (or click the field name, then the Contexts tab).
  2. Understand the default context. Every custom field has a default context that applies to all projects and issue types not covered by another context. You cannot delete it, but you can edit its default value and options.
  3. Create a new context. Click Add context (top right). Give it a name (e.g., “Bug Tracking”). Choose the projects and issue types this context will apply to. You can add multiple projects and multiple issue types. Click Add to create it.
  4. Set the default value for a context. In the context list, click the Edit (pencil) icon next to the context you want. Under Default value, enter the value that should be pre-filled when a user creates an issue in the projects/issue types of that context. Click Save.
  5. Edit available options for a context. For select-type fields (dropdown, radio, multi-select), click the Options tab within the context editor. Here you can add, edit, reorder, or deactivate options. These options are the only ones available in that context. Click Save after changes.
  6. Understand option inheritance. When you create a new context, it starts with the same options as the default context. If you edit options in one context, it does not affect other contexts. This allows you to have different option lists per project/issue type.
  7. Test your configuration. Create a test issue in a project that uses the context. Verify the default value appears and that only the options you defined are available. Repeat for a project not in the context to confirm the default context applies.
  8. Adjust context scope if needed. If a context is too broad or narrow, click Edit on the context and change the projects/issue types. Be careful—removing a project from a context will make it fall back to the default context, which may have different defaults/options.

Common Mistakes

  • Editing the default context when you meant to edit a specific one. Changes to the default context affect all projects not in another context, which can surprise you.
  • Forgetting that options are per-context. Adding an option to one context does not add it to others. You must add it to each context separately.
  • Setting a default value that is not in the options list. Jira will show an error or ignore it. Always ensure the default is one of the available options.
  • Overlapping contexts. If a project/issue type matches multiple contexts, Jira uses the most recently created context that matches. This can lead to unexpected behavior.
  • Not testing after changes. Always create a test issue to verify the behavior, especially after changing scope or options.

Tips

  • Use contexts to tailor fields for different teams. For example, a “Priority” field might have different options for IT vs. Marketing.
  • When creating a new context, plan its scope carefully. It’s easier to start with a narrow scope and expand than to fix overlapping contexts.
  • Use the Search bar in the context list to quickly find a context by name.
  • If you need to change options for many contexts, consider using the Bulk edit feature (if available) or the REST API for advanced automation.
  • Document your context structure (which projects use which context) to avoid confusion later.

Troubleshooting

  • Default value not appearing: Check that the context you edited is the one actually applying to the project/issue type. Verify the default value is in the options list. Clear your browser cache or refresh the page.
  • Options missing for a project: The project might be using a different context than you think. Go to the field’s Contexts page and see which context applies to that project. If none, it uses the default context—edit that.
  • Changes not saving: Ensure you click Save after editing. If you see an error, check for required fields or invalid option values.
  • Overlapping contexts causing wrong behavior: Review all contexts for the field. Delete or narrow the scope of the one that is taking precedence incorrectly.
  • Cannot edit options for a system field: Some system fields (like Summary) have restricted contexts. You can only manage contexts for custom fields.

Frequently Asked Questions

Can I have different default values for the same field in different projects?

Yes, by creating separate contexts for each project (or group of projects) and setting a different default value in each context.

What happens if a project is in two contexts?

Jira uses the most recently created context that matches the project and issue type. To avoid confusion, ensure contexts do not overlap.

Can I change the options for a field after issues have been created with old options?

Yes, but old issues will still display the old value. If you deactivate an option, it remains on existing issues but is not available for new ones.

Is it possible to have a context for only certain issue types?

Yes, when creating or editing a context, you can select specific issue types. The context will only apply to those issue types in the chosen projects.

How do I delete a context?

Go to the field’s Contexts page, click the three-dot menu next to the context, and select Delete. You cannot delete the default context.

Do contexts affect the field’s appearance on screens?

No, contexts control which projects/issue types the field is available in and its options/defaults. Screen schemes control where the field appears on the issue view.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.