Skip to content
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

Merged

Conversation

johannaengland
Copy link
Contributor

@johannaengland johannaengland commented Sep 6, 2023

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.

@johannaengland johannaengland self-assigned this Sep 6, 2023
@johannaengland johannaengland changed the title Show blacklisted reasonof alert address in alert profiles Show blacklisted reason of alert address in alert profiles Sep 6, 2023
@codecov
Copy link

codecov bot commented Sep 6, 2023

Codecov Report

Merging #2677 (842a6b0) into master (3ca7727) will not change coverage.
Report is 5 commits behind head on master.
The diff coverage is n/a.

@@           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

@github-actions
Copy link

github-actions bot commented Sep 6, 2023

Test results

     12 files       12 suites   14m 19s ⏱️
3 208 tests 3 208 ✔️ 0 💤 0
9 099 runs  9 099 ✔️ 0 💤 0

Results for commit 842a6b0.

♻️ This comment has been updated with latest results.

@lunkwill42 lunkwill42 force-pushed the show-blacklisted-reason-in-UI branch from e01d3aa to aea5b83 Compare September 7, 2023 09:33
"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.
Copy link
Member

@lunkwill42 lunkwill42 left a 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.

@sonarcloud
Copy link

sonarcloud bot commented Sep 7, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@lunkwill42 lunkwill42 merged commit 1192591 into Uninett:master Sep 7, 2023
11 checks passed
@johannaengland johannaengland deleted the show-blacklisted-reason-in-UI branch September 12, 2023 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feedback in AlertProfiles if address type is blacklisted
2 participants