Requested functionality :
Increase the number of possible ENUM and ENTITY_LINK custom fields that can be defined on an entity.
It should be possible to define 40 - 50 such fields.
Use case :
In our change management process, we have defined 12 qualification questions that allow the risk of a requested change to be assessed in a deterministic manner.
Answers to these questions are to be selected from a list of options.
We would like to save these answers in the change ticket.
However, given the current limit of 12 custom ENUM fields, and the need to add a few other ENUM fields, this is not currently possible.
We also reviewed the option to create a custom lookup table and use ENTITY_LINK type fields instead, but with the current limit of 15 custom ENTITY_LINK fields, this is not a sustainlable option, either.