As your team and the number of projects grows, you most likely need to use more custom fields to capture all the needed information on issues. Instead of creating a new field for each particular use case, you can configure contexts for the existing field and then reuse it as you see fit.

A context of a custom field is a combination of projects and issue types where that field can be used. For each context, you can choose:

• default values (what is pre-filled when a custom field is displayed)

• options (what users can choose from), only if the custom field type uses options

Set global and project-specific contexts

When you create a context or modify an existing one, you can select between two options:

• Set a global context — make the field available in every project that exists on your instance. This option won’t be available if the field already has a global context configured.

• Set a project-specific context — limit the field’s usage only to those projects where you actually need it.

You can set only one global context for a field and, if needed, change it to a project-specific one. However, there might be a case when you won’t be able to set another project-specific context for the field. This will happen if you add all projects available on your instance to one or more project-specific contexts.

If you set a global context for the field, you can still create project-specific contexts for the same field and add existing projects to those. In this case, project-specific contexts will override the global one in selected projects.

View field's contexts

You can view existing contexts for your field and add some new ones on the contexts configuration page:

1. In the upper-right corner of the screen, select Administration  > Issues.
   
   

2. Under Fields (the left-side panel), select Custom fields.

3. Find your custom field, and select Actions  > Configure to open the context configuration page.

1. Add new context: Here you can add a new context, or go back to the list of custom fields.

2. Default context: Details of the default context, with options, default value, and projects chosen when the custom field was created.

3. Another context: A new context for this field, with different options, default value, and projects.

Change the default context

When creating a custom field, you need to set the initial context for this field by selecting in which projects the field will appear. This context will become a default one for that field, which means that the field will be available only in the selected projects unless you create a new context or edit the default one.

The default context is called “Default context for <custom field’s name>” and you can modify it as any other context, changing a default value, options (if applicable), as well as issue types and projects where the field will be available.

Add a new context

Create a custom field context if you need to associate different default values and options with different projects or issue types.

To add a new context:

1. On the context configuration page, select Add new context.

2. Choose a name for this context. You can also add a description with any helpful information that'd give more details to other admins.

3. Add projects to this context. A field will be available in every project that you select in this context.

   If you want to move multiple items between lists, hold the Shift key while you select the items and then drag and drop them to the desired list. Or simply select Add or Remove.

4. Add issue types to this context. While you can search through all the issue types available on your instance, the field will be available only in issue types within the projects you’ve selected in the previous step.
5. Select Save.

This is what the page where you can configure a context looks like:

1. Name and description of the context you’re currently configuring.

2. Selected projects: All projects that belong to this context. When editing an existing context, you’ll see the Added now section with all projects you’ve just added but haven’t saved yet.

3. Available projects: Any projects that you can add to the context. This section might not contain all projects that exist on your instance - if some of them are selected in other project-specific contexts, they won’t appear in this list.

4. Multiple items selected in a list.

5. Selected issue types: All issue types that belong to this context. When editing an existing context, you’ll see the Added now section with all issue types you’ve just added but haven’t saved yet.

6. Available issue types: All issue types that exist on your instance.

Edit a context

1. Go to the context configuration page, and search for the context that you want to modify.

2. To change the details of this context, like name and description, and the issues and projects this context applies to, select Edit configuration.

3. Update the context as needed, and then save your changes.

Consider that projects that are used in other contexts (apart from the global one) won’t be available for selection.

Change field’s options and default value

To set up default values and options for the field in a context:

1. On the context configuration page, search for the context you want to configure.

2. To change the default value, select Edit default value.

3. To change the options, select Edit options. This will not be available for custom field types that don’t use options.

Delete a context

To delete a context:

1. On the context configuration page, find the needed context.

2. Select the delete icon next to the context that you want to remove.

When deleting a global context, remember that the field will be removed from all projects that aren’t selected in any other context.