The configuration has been added to both the organization settings (Settings > Configurations> Item Type Configurations) and project settings (Settings > Configuration settings >Item Type Configurations).
The check box Allow projects to edit configuration settings is included at the organization level. When selected, you can add or edit the configuration settings at the project level. When not selected, all fields in the project settings are disabled.
When editing at the project level is enabled, you can edit values at the project level to make fields more restrictive than they are at the organization level. For example, if a field is not required for a budget move at the organization level, you can configure it to be required for a budget move at the project level. When a field is required at the organization level, the field is disabled at the project level.
Require for budget move
When the Require for Budget Move toggle is set to Yes, the fields shown with an asterisk on details pages must be completed before you can submit a budget move.
Require for PCO or CCO association
When the Require for PCO association or Require for CCO association toggle is set to Yes, the fields shown with an asterisk on details pages must be completed before you can associate the issue to a PCO or CCO.
Lock after CCO association
When the Lock after CCO association field is set to Yes, you can no longer update the item at the issue level after it is associated to a CCO. The locked field and its value show on the Issue details, but the field is disabled. When a field is not locked, it is still affected by events, such as a workflow, that might lock the issue fields.
Read more
