Merge branch '22033-milestone-validation-returns-422' into 'master'
Ensure validation messages are shown within the milestone form
Fixes a bug where upon entering data to create an invalid milestone via the Web UI or the API would raise an exception rather than render the validation messages
We'd rather render the validation messages to inform the user than raise an exception and result in a 422 error being displayed
Closes #22033
See merge request !6345
Showing
Please
register
or
sign in
to comment