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.

Sign up for GitHub

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

Jump to bottom

Default auto-complete for the appointment end time according to service duration. #54

Closed
lucianpp opened this issue Sep 9, 2015 · 2 comments
Closed

Default auto-complete for the appointment end time according to service duration. #54

lucianpp opened this issue Sep 9, 2015 · 2 comments
Assignees
@alextselegidis
Labels
enhancement New feature or request
Milestone
v1.2.0

Comments

@lucianpp
Copy link

lucianpp commented Sep 9, 2015

Will be great if end time of an appointment in the backend will be populated by default according to the service duration. To be editable but completed by default!
How can I achieve this?
Thank you!
@alextselegidis
Copy link
Owner

alextselegidis commented Sep 23, 2015 •
edited
Loading

This can only be done with JavaScript. I'll implement it in one of the following releases.

@alextselegidis alextselegidis added the enhancement New feature or request label Oct 11, 2015
@alextselegidis alextselegidis added this to the v1.1.0 milestone Oct 11, 2015
@alextselegidis alextselegidis modified the milestones: v1.2.0, v1.1.0 Nov 23, 2015
@alextselegidis alextselegidis changed the title End time of appointment completed by default according to service duration Default auto-complete for the appointment end time according to service duration. Jan 21, 2016
@alextselegidis alextselegidis self-assigned this Jul 15, 2016
@alextselegidis
Copy link
Owner

Apparently the issue was fixed by another commit :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alextselegidis alextselegidis

Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.2.0
Development

No branches or pull requests
2 participants
@alextselegidis @lucianpp