Recurring appointments with cascading change propagation #9

Closed
opened 2026-03-17 14:58:12 +00:00 by ghost · 0 comments
ghost commented 2026-03-17 14:58:12 +00:00 (Migrated from github.com)

User Feedback

Many clients have standing appointments every 4-6 weeks. When one appointment instance changes (e.g., rescheduled), subsequent recurring instances often need to change as well. This is a significant pain point with existing tools — managing recurring appointment modifications is tedious and error-prone.

Requirements

  • Support recurring appointment series (e.g., every 4 weeks, every 6 weeks)
  • When editing a single instance in a series, offer the option to apply the change to all future instances
  • Allow exceptions to the series without breaking the recurrence pattern
  • Clear UI for viewing and managing the full series

Context

Related to #1 (Appointment & Schedule Management). Sourced from potential user feedback.

## User Feedback Many clients have standing appointments every 4-6 weeks. When one appointment instance changes (e.g., rescheduled), subsequent recurring instances often need to change as well. This is a significant pain point with existing tools — managing recurring appointment modifications is tedious and error-prone. ## Requirements - Support recurring appointment series (e.g., every 4 weeks, every 6 weeks) - When editing a single instance in a series, offer the option to apply the change to all future instances - Allow exceptions to the series without breaking the recurrence pattern - Clear UI for viewing and managing the full series ## Context Related to #1 (Appointment & Schedule Management). Sourced from potential user feedback.
This repo is archived. You cannot comment on issues.
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/app#9