Bonjour ! J’ai vu qu’il était possible de renseigner ses heures de travail pour informer les utilisateurs de mes disponibilités pour me joindre. Par contre, ce n’est pas très adapté pour les personnes travaillant en horaires variable, genre 2x8. Ce serait bien s’il était possible de créer plusieurs disponibilités selon la semaine (semaine paire, impaire, ou semaine 1, semaine 2…)
tcit
Février 5, 2024, 12:27
2
Bonjour,
J’ai trouvé ce ticket qui semble correspondre à vos besoins :
opened 06:21AM - 23 Aug 23 UTC
enhancement
1. to develop
feature: dav
feature: settings
feature: caldav
<!--
Thanks for reporting issues back to Nextcloud!
Note: This is the **issu… e tracker of Nextcloud**, please do NOT use this to get answers to your questions or get help for fixing your installation. This is a place to report bugs to developers, after your server has been debugged. You can find help debugging your system on our home user forums: https://help.nextcloud.com or, if you use Nextcloud in a large organization, ask our engineers on https://portal.nextcloud.com. See also https://nextcloud.com/support for support options.
Nextcloud is an open source project backed by Nextcloud GmbH. Most of our volunteers are home users and thus primarily care about issues that affect home users. Our paid engineers prioritize issues of our customers. If you are neither a home user nor a customer, consider paying somebody to fix your issue, do it yourself or become a customer.
Guidelines for submitting issues:
* Please search the existing issues first, it's likely that your issue was already reported or even fixed.
- Go to https://github.com/nextcloud and type any word in the top search/command bar. You probably see something like "We couldn’t find any repositories matching ..." then click "Issues" in the left navigation.
- You can also filter by appending e. g. "state:open" to the search string.
- More info on search syntax within github: https://help.github.com/articles/searching-issues
* This repository https://github.com/nextcloud/server/issues is *only* for issues within the Nextcloud Server code. This also includes the apps: files, encryption, external storage, sharing, deleted files, versions, LDAP, and WebDAV Auth
* SECURITY: Report any potential security bug to us via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/) instead of filing an issue in our bug tracker.
* The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization (https://github.com/nextcloud/)
-->
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are interested into the same feature.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
## Availability
The option to provide availability and based on that toggling DND is very helpful in my daily usage. However there is a problem with the availability times as for me they quite differ over the year and adjusting them every time is quite cumbersome. But for me they are easily groupable and being able to define different sets of availability and then being able to pick which one should be active atm would already solve it.
### My life example
* normal work:
- 6:00 - 7:30
- breakfast + bringing kids to kindergarten/school
- 8:30 - 12:45
- fetching kids + lunch
- 14:00 - 17:00
- tuesday only until 16:00 due to kids soccer and similar activities
- friday not available due to kids soccer and similar activities
- family time
- 20:30 - 22:00
- recovery time
* kindergarten/school holidays
- breakfast
- 7:30 - 12:15
- lunch
- 13:00 - 15:30
- family time
- 20:30 - 22:00
- recovery time
* Conference /contributor weeks:
- 8:00 - 0:00
- recovery time
## Problem
As you can see reconfiguring this multiple times per month can be quite cumbersome:
- From conf to work it's 8 time pickers per day (6 for friday) => 38 times picking an hour + minute slot and then outside to close the picker
- Work to school holiday => delete 1 slot and adjust 4 time pickers per day => 20 times picking
- One week later: school holiday to work => adjust 4 time pickers per day and add a new slot with 2 time pickers per day => 30 time pickers
So every time there is school holidays for a week, I wonder if ~50 time picker selections are worth it, or if I just leave my colleagues hanging with not being available/responsive although they checked my availability in the calendar and the user status right before reaching out.
## Solution proposal
As far as I can see we store the data in `oc_properties` with `{urn:ietf:params:xml:ns:caldav}calendar-availability`. Not sure if that would allow to have `{urn:ietf:params:xml:ns:caldav}calendar-availability-backup1` things in parallel and when switching the availability we simply do an update on the propertyname to enable/disable another set?
## Other solutions I considered
I configure the availability once store the propertyvalue into files locally and am using browser dev tools/curl to send a manipulated requests using the availability property I want for this week
Nous suivrons son évolution et nous nous y intéresserons si jamais il y a plus de demande.
1 « J'aime »