-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show blacklisted reason of alert address in alert profiles #2677
Show blacklisted reason of alert address in alert profiles #2677
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2677 +/- ##
=======================================
Coverage 55.03% 55.03%
=======================================
Files 561 561
Lines 40882 40882
=======================================
Hits 22498 22498
Misses 18384 18384 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
e01d3aa
to
aea5b83
Compare
"Blacklisting" is a very internal concept in AlertEngine. The net effect for users editing their profiles is that an alert sender is currently non-functional, for some reason. This changes the UI to just refer to the address types as currently non-functional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the outward term used in the UI from "blacklisted" to "non-functional", which is a more descriptive (and less harsh/technical) for the end user.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Closes #2653.
I modeled it after how it is shown when an alert sender is no longer supported, but used the warning box instead of the error box.
(basically copied 8b2700c)
Dependent on #2678.