- 
                Notifications
    
You must be signed in to change notification settings  - Fork 50
 
Open
Copy link
Labels
webFrontend/web related issueFrontend/web related issue
Description
Title
🐛 Someday recurring events edits should be committed on an individual basis
Description
Currently, when editing a recurring "someday" event in Compass, updating the attributes of an event in a future recurrence overwrites the attributes of the other events in the recurrence. This leads to a loss of event-specific details for other occurrences and prevents users from customizing individual instances.
Scope
- Alter the 
RecurringEventUpdateScopesent in the request payload to ensure edits only affect the targeted occurrence, not all recurrences. - Add/adjust relevant tests to verify that editing a single recurrence does not affect others in the series.
 
Acceptance criteria
- When a user edits a specific occurrence of a recurring "someday" event, only that instance is updated.
 - Other past and future occurrences remain unchanged.
 - Tests verify that editing one event does not propagate to others.
 
Business use case
Allowing users to edit individual occurrences of recurring events is critical for flexibility in planning and accurate record keeping. Users may want to rename or adjust a particular event without affecting the entire series, especially for events that evolve over time.
Additional context
- Solution: Alter the 
RecurringEventUpdateScopesent in the request payload to edit only the intended event. - See original bug report and discussion: Fix weekly recurrence in month 1087 #1095 (comment)
 - Reference Compass documentation: https://docs.compasscalendar.com/docs
 - Roadmap: 🏗 Compass Roadmap
 
Copilot
Metadata
Metadata
Assignees
Labels
webFrontend/web related issueFrontend/web related issue
Type
Projects
Status
Ready