Good morning everyone,
I am a new user of software for task management in different departments of a student association.

Using the Custom Fields feature, I think I have noticed a behavior that is different from what is described in the documentation (as I understand it) and in my opinion inconvenient.

When I create a non-global custom field, I have to activate it in a project and put it in the form of at least one work package. Here is where the problem arises: when I show the field in a work packages (e.g., task) it is automatically activated in all projects that have that type activated even though the custom field was previously disabled for them.
To date, the only workaround I have found is to then disable the custom field manually for each project where it is not needed. The same problem actually occurs with new projects (the custom field is immediately active) and that is why I have not found a solution yet.

The documentation I am referring to is this.
I do not classify the discussion as a bug because I am not sure it actually is one, in case I will provide more specific information on version and steps to reproduce the problem.

Thank you
Alex