nextcloud / nextcloud/calendar

After modifying a single instance of a recurring event, cannot move calendar

Open
#7,785 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. Create a recurring event
  2. Edit a single occurrence, and 'update this occurrence'
  3. This creates a standalone event, but cannot be moved to a different calendar
  4. Use "Duplicate" to make a copy of the event, and the duplicate is fully independent
Expected behavior

Ideally the event created after "Update this occurrence" would be fully editable as a standalone event

Actual behavior

The event has some of the properties of a standalone event (like working Duplicate button, which isn't available on recurring events), but not all (in particular, changing calendar)

Calendar app version

5.5.10

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

Nextcloud Hub 10 (31.0.8)

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

Reproduce the issue in the Calendar app by creating a recurring event, updating one occurrence, and trying to move it to another calendar. Compare the updated occurrence with a duplicated event; done means the updated occurrence can be moved as an independent event.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.