Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

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:

(tick) Do's

(error) Don'ts

Create unique contexts for fields that are used by multiple projects.

Keep all of your custom fields in a global context when they’re used by more than one project.

Project map custom fields that will need to be updated by your team frequently.

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 →

  • No labels