nextcloud / nextcloud/deck

Using the same name as an existing calendar _deleted_ the original calendar/task list

Open
#3,694 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: dav
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Describe the bug
Started a Personal deck, with my primary calendar named Personal and a task list as Personal. This deleted the original calender somehow in the migration/removal of a task list of the same name, and once the Deck name changed, somehow the Personal account was lost my-instance-of-nextcloud.com/remote.php/dav/calendars/user/personal/ was a 404 at first or mobile (DAVx5), and then reappeared on the webapp. 🤷

All data seems to be lost 😭

To Reproduce
Steps to reproduce the behavior:

  1. create a deck with the same name as an exiting calendar / task
  2. delete the task list
  3. calendar is also removed
  4. Deck remains

Expected behavior
NEVER straight loose data based on a name conflict, without warning. No way to undo/recover.

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 reported sequence: create a Deck with the same name as an existing calendar or task list, delete the task list, and check whether the calendar remains. Trace the Deck task-list migration/removal path and its handling of name conflicts. Done means the existing calendar and its data are preserved, with a warning or recovery path when names conflict.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.