-
Notifications
You must be signed in to change notification settings - Fork 9
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
Existing events in my calendar do not seem to be considered for availability #819
Comments
Hi Laurent, thank you for this report, I can indeed reproduce this with a CalDAV Nextcloud instance for testing purposes. No calendar events are shown in the schedule view (hence no blockers in the booking view) from CalDAV calendars. @MelissaAutumn When checking back to #707, the events are there again. We might have broken it somewhere in between 😅 I'll look into this. |
FYI: #707 is now merged, this can be tested with the next release. |
The next release will hopefully be later this week once I find some time to thoroughly test stage. |
Hey there @laurentS, apologies for the delay. We've just released the latest update that should help with availability. Can you give it a test and see if it is working or if it's still broken? Thanks! |
I had and unfortunately still have the same problem with CalDAV / SOGo. |
I can confirm that appointment.day is taking consideration of my nextcloud calender and marking me as busy for that date and time! |
Are you events marked as Busy (or otherwise known as Opaque iirc)? Non-busy/transparent events aren't considered for your availability. |
They are marked as busy (both in SOGo and when I import the calendar in Thunderbird). |
Describe the bug
I am able to book an appointment during a conflicting event in my calendar. I would expect this not to be possible.
None of my existing events seem to be considered for my availability.
To Reproduce
Steps to reproduce the behavior:
(only tested on https://appointment.day/ as deployed at the time of this issue creation)
My calendar is a caldav shared from a private nextcloud instance.
Expected behavior
Time slots that conflict with events in the calendar should not be available to book.
Actual behavior
I am able to book appointment during any of the existing events in my calendar.
System (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: