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 2 Next »

(tick) Do's

(error) Don'ts

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.

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.


Check out the Do’s and Don’ts when mapping fields to a project

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.