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

Improve speaker notification email handling #1351

Closed
2 of 3 tasks
rixx opened this issue Sep 10, 2022 · 0 comments
Closed
2 of 3 tasks

Improve speaker notification email handling #1351

rixx opened this issue Sep 10, 2022 · 0 comments
Labels
size: big or difficult Will take a long time and/or a lot of skill sponsorship This issue is well-suited to be sponsored. You can read more at docs.pretalx.org/funding stage: up for grabs type: feature type: ux

Comments

@rixx
Copy link
Member

rixx commented Sep 10, 2022

We need to improve how speaker notification emails handle for organisers. They currently lead to occasional trouble and make organisers sad or confused or both.

  • Explain on the schedule release page that notifications won't be sent out immediately, and rather be placed in the outbox.
  • Make it easy to see and change the schedule update email template on the schedule release page, either by linking or by embedding the form.
  • On the "re-send speaker notifications" action (which is fairly hidden, but that's a different problem), allow two modes: "Notify all speakers of all their times" and "Notify only changed speakers of their changes". This is necessary because organises will release their first schedule without generating notifications, then release one or two corrections, and then they'll want to send out notifications. UPDATE: We now have email placeholders both for speaker_schedule_new and speaker_schedule_full, so we only need to explain here that to send full updates to speakers, they can send an email directly to all confirmed/scheduled speakers.
@rixx rixx added the sponsorship This issue is well-suited to be sponsored. You can read more at docs.pretalx.org/funding label Jul 13, 2023
rixx added a commit that referenced this issue Jan 31, 2024
rixx added a commit that referenced this issue Jan 31, 2024
@rixx rixx closed this as completed Feb 8, 2024
rixx added a commit that referenced this issue Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size: big or difficult Will take a long time and/or a lot of skill sponsorship This issue is well-suited to be sponsored. You can read more at docs.pretalx.org/funding stage: up for grabs type: feature type: ux
Projects
None yet
Development

No branches or pull requests

1 participant