Draft: When quick action fails, use danger variant for alert
What does this MR do and why?
When a quick action in markdown fails, the alert should use the 'danger' variant, not the 'info' variant.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Scenario | Before | After |
---|---|---|
Successful quick action (no change) | ![]() |
![]() |
Failed quick action | ![]() |
![]() |
How to set up and validate locally
- Check out this branch locally
- in an issue or MR, try to use the
/assign
quick action to assign to a nonexistent user - You will see that the alert created is a danger variant alert
- now use the same quick action to assign to an existing user
- you will see that the alert uses the info variant
Related to #382799