Skip to content

Use high priority sending for activation emails

Alex requested to merge high-priority-activation-email into master

Followup from !1334 (merged)

What does this MR do?

Sets activation emails to high priority, so that they are put at the front of the queue.

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

Should work

How to test

Steps a reviewer can take to verify that this MR does what it says it does e.g.

  1. Checkout branch locally
  2. Set active=0 for a user in fs_foodsaver?
  3. Login as that user
  4. Click on the link in the dashboard notification for a new activation email
  5. Check http://localhost:18084 if the email is sent

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.)

Merge request reports