[Bug]: Deleting/Canceling an Instance of a Recurring Event Generates an Unhelpful iMIP Message
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Bug description
Deleting/Canceling an Instance of a Recurring Event Generates an Unhelpful iMIP Message
Steps to reproduce
- Create an event and configure it to repeat weekly.
- Add Alice as an attendee.
- Select one instance of the recurring event and delete/cancel it.
- Observe that Alice receives a generic email stating that the event was updated, but the information specifying that only that particular instance was canceled is missing.
Expected behavior
Alice should receive a clear and specific notification indicating that a particular instance of the recurring event has been canceled, rather than a generic update message.
Additional info
By comparing the exdate, it is possible to determine the reason for the update and generate a more informative iMIP message. This will help attendees understand exactly which instance of the event has been canceled.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified in the issue. Reproduce the recurring-event cancellation, then trace how exdate changes are handled when the iMIP message is generated; done means attendees receive a message identifying the canceled instance rather than a generic update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100