Skip to content

Recurring bookings with "byweekday" repetition #5806

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

Closed
ThiefMaster opened this issue Jun 8, 2023 · 1 comment · Fixed by #5829
Closed

Recurring bookings with "byweekday" repetition #5806

ThiefMaster opened this issue Jun 8, 2023 · 1 comment · Fixed by #5829
Assignees
Milestone

Comments

@ThiefMaster
Copy link
Member

  • Support "byweekday" rules for recurring bookings
  • Add new UI widget to select weekdays

An example for such a recurring booking would be "weekly, monday+tuesday". Right now the only way to do this would be making two separate bookings, which is not user-friendly.

Related tasks for the Burotel CERN plugin (these do NOT need to be done at the same time, but depend on this being done in the core):

  • Allow weekly repetition (currently: only daily repetition)
  • Verify correct ADaMS sync (should still cover the whole period)
@ThiefMaster
Copy link
Member Author

As discussed offline, this should be an extension to the "recurring" booking. Below the "every [n] [weeks|months]" there would be a button group (or similar) that shows the 7 week days, with the one of the start day always being selected (since it would be pointless to exclude it). You can then add additional weekdays if you want, and those would be included in the booking.

On the server side this would simply affect the rrule. You likely need a new column (postgres array of strings?) to store the weekdays. for this one I think nullable=true makes sense (and keeping it null for single/daily bookings, maybe a check constraint to enforce this).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants