nextcloud / nextcloud/calendar
User migration creates a second birthday calendar that can't be removed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Use User Migration app to export calendars from a Nextcloud instance
- Important the file in a new user on a fresh Nextcloud instance
- Observe that there are now two Birthday calendars; one disappears when turning off the birthday calendar, but the other (migrated-contact_birthdays) stays, and does not sync with new contacts
- Press Delete on the calendar, it gets struck through, but on a page refresh it is back
Expected behavior
The Birthdays calendar probably shouldn't be migrated at all. It seems like the newly generated Birthdays calendar works perfectly with my migrated contacts.
Actual behavior
I now have two birthday calendars (I'm guessing I can remove the other with an OCC command or similar, but I still feel this can be improved by not migrating it at all, or allowing it to be removed
Calendar app version
6.5.3
CalDAV-clients used
Thunderbird, DAVx5
Browser
Firefox 153
Client operating system
Ubuntu
Server operating system
Debian 13
Web server
Apache
Database engine version
No response
PHP engine version
No response
Nextcloud version
Nextcloud Hub 26
Updated from an older installed version or fresh install
No response
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
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
Start by reproducing the export and import sequence with the User Migration app, then inspect how the migrated contact_birthdays calendar is handled. Done means the migration no longer creates a duplicate Birthday calendar, or the migrated calendar can be deleted and stays removed after a refresh.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100