Mapped custom fields can impact other projects if they’re configured in global contextos.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:
| |
|---|---|
Create unique contexts for fields that are used by multiple projects. | Keep all of your custom fields in single a global context when they’re they may be used by more than one project.Project map multiple projects |
Map custom fields that will need to be updated by your team frequentlyto 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. |
Do's
Don'tsNAVIGATE THROUGH OUR DOCUMENTATION:
← ACCESSING A PROJECT THROUGH THE ADMIN PAGE | OPTION MANAGEMENT →