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:
|
|
|---|---|
Map 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 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. |
Do's
Don'ts
Add Comment