Skip to content

Button for removing users from email bounce list

Alex requested to merge remove-from-bounce-button into master

What does this MR do?

Adds a button to the profile page that allows removing the user's email address from the bounce list. The button is only visible for orga if the user is on the bounce list. I reimplemented the whole warning component in vue (see screenshot below).

TODO:

  • show the bounce reason next to the button
  • give rights to a specific working group

How confident are you it won't break things if deployed?

quite sure

How to test

add some bounces for user2 in phpMyAdmin:

INSERT INTO `fs_email_bounces` (`email`, `bounced_at`, `bounce_category`)
VALUES ('user2@example.com',NOW() - 10,'full'),
       ('user2@example.com',NOW() - 20,'autoreply'),
       ('user2@example.com',NOW() - 30,'outofoffice')
  1. Checkout branch locally
  2. Login as user2
  3. Go to your profile: http://localhost:18080/profile/2
  4. You should see the warning (first screenshot)
  1. Login as userorga or userbot
  2. Go to user2's profile
  3. You should be able to see the bounce events
  4. Click the button to remove the user from the bounce lists
  5. After the page reloads the events should be gone

Screenshots (if applicable)

On your own profile: notice

On someone else's profile for orga and admins of the support group: warning_orga

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • use "state:" labels to track this MR's state until it was beta tested
  • added an entry to CHANGELOG.md
  • add a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo:
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...). how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text

(A short text that will appear in the release notes and describes the change for non-technical people. Not always necessary, e.g. not for refactoring.)

Edited by Alex

Merge request reports