✍️ Step-by-Step
When associating After adding a custom field with a to your project mapping, an alert the message below will appear if requesting to associate the custom added field does not have to a specific context for this project. :
...
At this point you will have the option of creating a specific context for this project or keeping the project in the global contextHere, you can either choose to keep in on the global context or add a new context specifically for the project you’re associating the field to.
...
📝 Important Tips
When we split a context, we can have different lists of options for the same custom field.
When a custom field is in the global context, a globe symbol '🌐' will appear next to the custom field's name.If you choose to keep your field on global context, any changes made later on will reflect on other projects currently using that field.
If you choose to create a new context for the project you’re mapping your custom field to, it will be automatically associated to the current project after created, and any changes made to the field will be limited to its context.
There will be a 🌐 icon next to custom fields in global contexts.
NAVIGATE THROUGH OUR DOCUMENTATION:
← ASSOCIATING CUSTOM FIELDS TO PROJECTS | BEST MAPPING PRACTICES →