When associating custom fields to project, it’s essential to remember that any changes made to their set of options can impact other projects depending on your configuration. Below, we listed the best practices when project mapping your custom fields as to reduce any side effects on other projects that might also be using them and to avoid overcharging your project administrator:
...
Associate Custom Fields with Projects
This page allows you to link specific Custom Fields to individual projects, granting project administrators the ability to edit and customize those particular fields.
...
| |
|---|
Map a custom field to a project it is only used by it
Map a custom field
Include only the necessary custom fields.
Check if the associated custom fields impact other projects.
Create unique contexts for each project to avoid interference across different projects.
Bad practices ❌
Include custom fields that should not be edited.
Associate the custom fields only with global contexts.
Create unique contexts for fields that are used by multiple projects. | Keep all of your custom fields in single a global context when they may be used by multiple projects |
Map custom fields to projects that requires frequent upgrades. | Map custom fields that should have a fixed set of options or should only be managed by a Jira Admin. |
Map relevant custom fields. | Map custom fields that won’t be used in your project. |
NAVIGATE THROUGH OUR DOCUMENTATION:
← ACCESSING A PROJECT THROUGH THE ADMIN PAGE | OPTION MANAGEMENT →