-
Notifications
You must be signed in to change notification settings - Fork 19
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
[Feature Request] Add RemindOperation to settings #22
Labels
Comments
for wait u can change timer in tabs on |
Yep. Feature really needed. Too many people disabling notification due this. |
alkari-verende
added a commit
to alkari-verende/eveseat-calendar
that referenced
this issue
Jan 1, 2022
This addresses one of the top comments in issues reported to the calendar: allow admins to control when and how often operations are pinged out. Closes BenHUET#22
warlof
pushed a commit
that referenced
this issue
Jan 3, 2022
* Add settings to enable/disable operation notification types Several users have requested the ability to reduce the number of notifications sent via the calendar. This commit adds the ability to globally disable each type of notification: create/post, update/edit, cancel, activate, end. * Allow configuring intervals for operation pings This addresses one of the top comments in issues reported to the calendar: allow admins to control when and how often operations are pinged out. Closes #22
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow for the RemindOperation job to be set in Settings so that an admin can choose at what intervals reminders should be sent.
An example from my particular situation:
Currently we don't use the Slack integration at all as the Reminder pings are intrusive at the current 60,30,15 mins before kickoff. Ideally for us there would be no ping when an OP is set (or a post to Slack without a
@everyone
tag, then a single ping 5 minutes before the OP forms and that's it. Having this configurable would let us use the slack integration.The text was updated successfully, but these errors were encountered: