-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Allow the users to define their own status and assign them to appointments. #244
Comments
Marked as a an enhancement, thanks :) |
Thanks for posting! I think a nice idea would be is we could make these statuses dynamic in the settings page. Like a small management list would be great 👍
|
Yeah, a management list would be great. But if we want the admins to define these statuses, we have to make the input (status text) language agnosticism right? Another way is we define several statuses and let the admins decide which ones to use. |
Yeah you are right, I guess this would be extra work for us so maybe it's better to keep you initial solution with the predefined statuses that can easily be translated. In the future we might add the ability to add custom statuses.
|
I think that the best solution would be to integrate the select box in the event popup, and update the value with an AJAX request. If you find this too much then I would just let the user to modify the event by opening the editing modal. The button could work, but I think that it can be frustrating because you cannot set all the possible statuses. I mean jump from one status to the other without clicking too many times.
|
Yeah colored events look good! The dots won't be visible if the appointment duration is short so I would skip that. Good Job :)
|
I did a pull request that finished most of the job, but I did a update from an older version, the database left unchanged (didn't update the schema). #252. About the color of events, let's use
Any better idea? |
And for the appointment statuses, colored events card look good, but will we need the colors for other purpose in the future? or just use them as status indicators? To me, if there is a multi calendar feature coming out (e.g.: login as an admin, each calendar is for one provider), the colors will be useful to distinguish them. And yes, The dots also won't be visible if 2 appointments are overlapped. |
Me and my colleague @ikangiec now think the status may not be the best idea to deal with appointment check in problem. Maybe split them to user's action (Yes, No, Maybe) and admin's action (Check In), or simplify the current status to just Please hold onto the pull request for now until we come up with a better solution. |
Ok first things first, for now we can use colors for showing the current appointment status as there won't be any multi-calendar feature soon. It is quite possible that it will come in the future but then we will probably change the status display by using some icons, tags/labels or maybe plain text. For you second question I cannot see why an appointment status won't solve your original problem. It's a really easy way for admins to keep this info without modifying the appointment notes. The customer has also the ability to cancel an appointment.
|
Agree, colors for appointment status is still the best solution for now. You are right, the status can solve our original problem. The customer can cancel an appointment, the admin can also delete them, so our option We wanted to simplify this, after checking with other softwares online, we think we only need to store the check in status. I mean, something like this: Status: Colored appointments are still useful, but if we go with the |
Did another pull request, hope you will like this solution :) The statuses are still there, just left only registered and checked_in. |
@rankun203 Thanks for the work. |
If we only have two statuses then it's true that we only need two colors. I'll some time to elaborate on this but I will post here soon (after reviewing the pull request). In any case though I would like to thank you for your contribution :)
|
I would also appreciate to set a default behavior after confirming the transition state.
|
@supersmart-at Right, there are many things that can be triggered by status changes and they all make sense, based on the workflows of each company/professional. Easy!Appointments will always aims to provide the best tooling for any use case. For your case, I think that the following steps would work as well:
|
Pushed in develop branch.
|
The ability to mark an appointment as
checked-in
,completed
.The text was updated successfully, but these errors were encountered: