nextcloud / nextcloud/calendar

Free-Busy glitches

Open
#6,846 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage bug Feature: Scheduling
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce

Everything tried on c.nc.com

  1. try to book a appointment with one of your colleague for 1 hour (this is important to chose a meeting longer than 30 min!)

Image

  1. After you added a attendee, go to "Find a time"

  2. First it looks good, a 1 hour slot is selected:
    Image

  3. Now select a different timeslot

Image

First glitch: Now it only selects a 30 min slot

  1. Chose one of the new selected timeslot by clicking on "Done"

Image

Second glitch: The "Find a time" dialog closes but the new selected time is not applied. The event still shows the initial date/time (compare the screenshot from step1 and step5, they are the same)

Expected behavior

see above

Actual behavior

see above

Calendar app version

No response

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

No response

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the flow on c.nc.com: create a one-hour appointment, add an attendee, open “Find a time,” and select another slot. Compare the selected duration and the event’s resulting date/time; done means a new slot preserves the one-hour duration and is applied after clicking “Done.”

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.