nextcloud / nextcloud/calendar
Recurring events can be dragged & dropped and break the series in the web UI, not on caldav
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
When a user creates a recurring event and tries to modify an occurrence of the event, they are asked if the user wants to modify the series of the occurrence.
Expected behaviour
When an event is being moved with the mouse the user should be asked if he/she wants to change the whole series, the current occurrence only or the occurrence and the future ones and the series shouldn't be broken.
Actual behaviour
When the user moves an occurrence around with the mouse, no such thing is being asked. After moving the occurrence with the mouse, the occurrence doesn't appears are one. It's now being handled as a single event while the other occurrences of the series are still handled as such. On the caldav interface the 3 events are still being linked.
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 reproducing the issue in the web UI with a recurring event, then compare mouse drag-and-drop with the existing occurrence-modification flow. Done means moving an occurrence presents choices for the series, current occurrence, or future occurrences, while the series remains linked as it does through CalDAV.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100