mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-22 21:15:18 -05:00
Kanban reset when syncing with CalDAV #1838
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vikunja#1838
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kattelk on GitHub (Dec 19, 2022).
Description
When syncing lists from Vikunja to CalDAV, all tasks in the Kanban view move to the Backlog list.
On both my own system and the demo system, it occurred the first time Vikunja was connected to CalDAV. Seems to occur less often as I continue testing.
Vikunja Frontend Version
0.20.2+3-f152a84847
Vikunja API Version
v0.20.1+34-6a97a214a3
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
Yes
Screenshots
No response
@kolaente commented on GitHub (Dec 19, 2022):
Does this happen with all tasks or only those who are updated?
@kattelk commented on GitHub (Dec 23, 2022):
It is not just the updated tasks. I can't consistently get this phenomenon to occur after the first sync, but it can (and does often) occur when new tasks are added and synced, and when the frontend is not showing the kanban view (showing the kanban view seems to "protect" it during the sync).
@kolaente commented on GitHub (Dec 23, 2022):
So this does only affect new tasks?
This should not make any difference.
@kattelk commented on GitHub (Dec 23, 2022):
No, it does not only affect the new tasks, but it seems to only affect lists where there are new tasks.
@kolaente commented on GitHub (Dec 24, 2022):
Should be fixed in
194b88e2eb- please check with the next unstable build once it's ready.