When associating custom fields to project, it’s important 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:
...
|
|
|---|---|
Map a custom field to a project it is only used by it | Map a custom field |
Do's
Don'ts...
Include only the necessary custom fields.
custom fields that might need new options frequently. | Map custom fields that have a fixed set of options and should not be freely edited. |
Create unique contexts for |
...
Bad practices ❌
Include custom fields that should not be edited.
Associate the custom fields only with global contexts.
...
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.
...
fields that are used by multiple projects. | Keep all your custom fields on global context. |
Associate only custom fields you’re sure your team will use. | Add unnecessary custom fields that aren’t used in your project or that won’t need to be managed by your project administrator. |