Tymeslot - Feature Requests?
-
Biggest Feature would probably be Teams with automatic routing etc.
-
Biggest Feature would probably be Teams with automatic routing etc.
Biggest Feature would probably be Teams with automatic routing etc.
I have started working on it, but expect it will take a few more weeks until it can be reliably shipped.
Exchange Webservices as as additional calendar type would be nice, but there does not seem to be something in elixir for this.
That's not an issue! That can also be done in the foreseeable future.
-
@ekevu123 Thanks for this - Tymeslot is a very nice product and is turning into a worthy alternative to Cal.com more and more everyday, soon to surpass it.
I had suggested a couple of features on github (almost all implemented!), but here are some additional ones, more or less "enterprise" targeted ideas:
- Administer other users/user parameters (possibly also impersonating user)
- possibility to enforce theming across team/organisation
- possibility to enforce certain parameters (booking link format scheme, availabilities constraint / working times, timezones etc...)
- Work with multiple domains
- Work with multiple orgs (maybe via/with a superadmin role)
- theming dashboard/login page
- Dark mode
- SSO provider naming (the login page only present the "continue with "SSO" option, It would be great if it could use the SSO provider name - via env variable I believe - as per most other Cloudron OIDC enable apps)
- for each availability period (or meeting type?): date override -> adding exception to availabilities / overruling of availabilities. e.g. available mon-fri 9:00-11:00 -> except fri 28/08
- booking via QR codes (maybe it is there already but could not find it)
Just some ideas, possibly not all of them/none of them are worth it and/or not implementable.
Or some you might already have in the pipeline.Once again - Thanks for the app!
-
the
time-slot intervalsis a great feature of cal.com
It ends in :
This will be deployed this week!
Exchange Webservices as as additional calendar type would be nice, but there does not seem to be something in elixir for this.
This as well, but I couldn't test this well myself, feel free to check it out. I used an open-source exchange server for testing.
-
I made a quick smoke test against our ews implementation. Single and recurring meetings seem to be shown at the right place. Its of course a pity that the calendar is not writeable, but I understand that this would also add more complexity.
In regards to the read only calendars I noticed that you still have the delete button on an event in such a calendar. clicking it then gives an error toast notification. It would probably better to signal the read only state already to the event detail screen.
Another thing I noticed (but i dont think its new) is that whenever you trigger a manual sync from the calendar view, the view always jumps to 0:00 once it has completed.
-
Feature request: easier handling/setting of env variables in Cloudron Package.
Right now, one need to use the Cloudron CLI to add env variables.
It would be great if the Cloudron package was integrating the more traditional way to do this, as discussed here, maybe have a default .env file at the root of the package, matching the one here depending on what is expos(ed/able) or not
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login