Add character validation for custom status names
What does this MR do and why?
Prevent leading/trailing quotes, backticks and control characters in work item custom status names to avoid parsing conflicts with quick actions.
Model validation and a database constraint ensure that only new records, or existing records during an update, are validated.
We will not introduce any background batch migrations to update existing invalid custom status names.
References
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Navigate to the work item statuses settings page at the root group level, for example:
/groups/flightjs/-/settings/issues. - Trigger a validation error by attempting to create or update a status using a name that contains unsupported characters, for example
"Invalid status"or"Invalid/nstatus".
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Agnes Slota