Bug: Alert errors aren't visible after first dismissal
Summary
It is possible to dismiss errors on the Alert Management list view.
When one error is dismissed, it will not appear again.
This may cause confusion for some users.
Steps to reproduce
This will reproduce it via the "An alert with the same fingerprint is already open" error.
- Set up alerts on a project in GitLab
- Send an alert to the endpoint. e.g.
curl --request POST \ --data '{ "title": "Example recent alert" }' \ --header "Authorization: Bearer <<API TOKEN>>" \ --header "Content-Type: application/json" \ <<ALERT ENDPOINT>>
- In the alert list, (
https://<base-url>/<project>/-/alert_management
) Resolve the alert via the dropdown on the left. - Send an identical alert to the one earlier.
- Navigate to the 'Resolved' tab of the alert list.
- Unresolve the alert.
- Dismiss the error.
- Unresolve the alert again.
(see video below for steps 5. thru 8.)
Example Project
https://gitlab.com/gitlab-org/monitor/tanuki-inc/-/alert_management
What is the current bug behavior?
- The action fails but no error appears.
What is the expected correct behavior?
- The action fails and an appropriate error message appears.
Relevant logs and/or screenshots
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)