Currently, the SQL schema uses varchar for enumerations.

Identified cases:

• service.status
• incident.status

It could be interesting to arbitrate between:

• keep to use strings as identifier for enum handled at back-end level
• switch to use enum, so db can validate values
• use an extra table to store the different field values and allow extensibility: each project can add their own categories according their internal needs