nextcloud / nextcloud/calendar
Make out of office event read-only
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Is your feature request related to a problem? Please describe.
When creating an ouf of office message in the Absence section of the Availability settings, an event with status busy will be created in your "Personal" calendar.
It is irritating, that I can edit this event inside my calendar (like moving it around, renaming, editing the title or the description, ...) and it has no effect on the out of office settings in the Absence section of the Availability settings.
As a user I would expect the out of office setting and the event to be linked and thus in sync.
Describe the solution you'd like
The calendar event could just be read-only in the calendar and so the user can edit it via the out of office settings and it always stays in sync.
Also, a small extra suggestion: It would be nice to make the calendar event an all-day event instead of starting it at 00:00.
Describe alternatives you've considered
Another way would be to make the sync work both ways - so when the calendar event gets changed, the out of office settings get updated. But I can imagine that it would be rather complicated.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Absence section under Availability creates the busy event in the Personal calendar. Check the existing calendar event behavior and the connection back to the out-of-office settings. Done means the generated event cannot be edited in the calendar and the requested all-day behavior is addressed without breaking the settings flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100