Skip to content
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

Appointment modal start/end time initially set to slotDuration rather than service duration #1449

Open
mynameisjonas opened this issue Jan 16, 2024 · 3 comments

Comments

@mynameisjonas
Copy link

Hi Alex,

Our providers often book appointments over the phone or in person and therefore use the backend to create a new appointment.

They do this by clicking on the calendar time slot that brings up the backend appointment modal window.

Something we have noticed is that when form loads the Start Date/Time and End Date/Time defaults to the slotDuration of the calendar which in our deployment we have set to 30min. This happens even if the Service and Provider have "default" values (the provider being populated with a value provided the calendar view is not set to "All")

Most services are longer that this and the most common service duration is 45mins.

The provider needs remember to change the Service to something else then change it back again in order to get the correct duration before saving the form otherwise the appointment will be booked with the incorrect duration.

I've tested this behaviour with 1.5.0 dev 4.

One workaround would be to clear the Service option value when the form is initialised so that the provider always needs to select something. Is that a relatively easy code change?

Many thanks for all your hard work on this project!

mynameisjonas

@mynameisjonas mynameisjonas changed the title Appointment model appointment start/end time initially set to slotDuration rather than service duration Appointment modal start/end time initially set to slotDuration rather than service duration Jan 16, 2024
@mynameisjonas
Copy link
Author

mynameisjonas commented Jan 16, 2024

An example here from the public demo @ 1.4.3. Clicking on the calendar slot (where the default slot is 15mins) means the start/end duration is initially set to 15mins even though the service is 30mins

image

@alextselegidis
Copy link
Owner

alextselegidis commented Jan 22, 2024

Hello!

That is correct, the calendar widget will try to set start/end values based on what was selected in the calendar.

In some cases that makes sense as it will save the user from typing in that manually.

In other cases (like yours) that would be a problem, cause you would not care about the calendar selection but on the selected service.

I guess a compromise will make it so that if the user clicks and not click and drag in the calendar, the default times will be selected

Alex Tselegidis, Easy!Appointments Creator
Need a customization? Get a free quote!

@mynameisjonas
Copy link
Author

Hi Alex,

Yes I think that would make sense - if the user single clicks a specific time slot then use the selected start time + service duration to calculate end time of the appointment. A click and drag is perhaps a more intentional action and implies the person making the booking has a specific appointment duration in mind.

Keep up the great work and congrats on the 10 year milestone !

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

No branches or pull requests

2 participants