-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.2.7
-
Component/s: Apps - Team Calendar
-
None
-
1
-
Severity 3 - Minor
-
0
Issue Summary
When clicking the "Turn off reminder" link in the e-mail a second time, the reminder will actually be turned on again, according to the message that appears in Confluence: "You've turned on reminders for {Event Type} in {Calendar Name}
". Clicking it a third time will again produce the same "on" message, so it seems that disabling the reminders only works when clicking the link the first time. Clicking it again (which may happen by accident) enables them again, but should instead keep them disabled and show a message along the lines of "Reminders for
... : {Event Type}
in
... : {Calendar Name}
are already disabled".
Steps to Reproduce
- Set up your mail server for Confluence notifications under General Configuration > Mail Servers
- Browse to Calendars in the Confluence header
- Create a new Calendar
- Define a new event with a Start time in the next 30 minutes, and set the Reminder as "5 minutes before"
- On the menu close to "Events," ensure the reminders are turned on.
- If they are actually set, you will see "Turn off reminders" as a menu option.
- Wait until you receive a mail notification in your inbox about the Event you just configured.
- The mail notification includes a link on the top right side called "Turn off reminder." Click this link to unsubscribe from future notifications.
- Clicking on it, will Turn off the Reminder and you will not receive email reminder. However if you click on the Turn off reminder button again in the email, the reminder are turned on
Expected Results
Clicking it again (which may happen by accident) enables them again, but should instead keep them disabled and show a message along the lines of "Reminders for
in
: {Calendar Name}
are already disabled".
Actual Results
Clicking again on Turn off reminder turns on the reminder as shown on the UI
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...