nextcloud / nextcloud/calendar
Updating an event with room details needs a page refresh for the update to be shown
Open
Nobody has claimed this yet.
0. to triage
bug
Feature: Rooms and Resources
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Create an event with a CalDAV client. I tried with Thunderbird.
- Go to the Calendar UI and add a room to the event, then click update
- Reopen the event, the status of the room is still shown as "Checking Availability"
- Refresh the page (F5) and reopen the event, now the status of the room is correctly updated.
Expected behavior
The status of the room should be updated after step 2. This happens when the events are created directly in the Calendar UI.
Actual behaviour
The status of the room is updated after a page refresh
Calendar app version
c.nc.com
CalDAV-clients used
Thunderbird
Browser
Firefox 100
Client operating system
Ubuntu
Server operating system
c.nc.com
Web server
No response
Database engine version
No response
PHP engine version
No response
Nextcloud version
c.nc.com
Updated from an older installed version or fresh install
No response
List of activated apps
c.nc.com
Nextcloud configuration
c.nc.com
Web server error log
c.nc.com
Log file
c.nc.com
Browser log
c.nc.com
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
No source file or test is named in the report. Reproduce the Thunderbird-created event flow, add a room in the Calendar UI, and compare the update behavior with and without a page refresh; done means the room status changes from "Checking Availability" immediately after saving.
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