nextcloud / nextcloud/calendar
The availability of participants, resources and rooms incorrectly indicates the employment of the event participants.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- I'm opening my calendar. I immediately want to write that I do not keep my own calendar, and my time frame is 95% free.
- I select some time on the calendar with the mouse.
- I press the "More details" button
- I go to the "Participants" tab and add one colleague.
- I press the "Find a time" button.
Expected behavior
It was expected that this setting would display my download correctly, relative to the data that is filled in the calendar for me and my colleague.
Actual behaviour
I see the following information about myself, I have been busy all day, it is displayed in red. Although this is not the case.
Calendar app version
4.7.16
CalDAV-clients used
No response
Browser
Firefox, Yandex
Client operating system
Windows
Server operating system
Linux
Web server
Nginx
Database engine version
MySQL
PHP engine version
Other
Nextcloud version
28.0.11 - 28.0.11.1
Updated from an older installed version or fresh install
None
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
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 in the Calendar app by reproducing the flow through the Participants tab and the “Find a time” button with the reported version and browser details. Compare the displayed availability for the reporter and colleague with their calendar data; done means the availability no longer marks the reporter busy all day when the calendar is mostly free.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100