github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-08 21:08:04 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

CalDAV subtasks in Tasks (Android) or jtx Board #2587

New Issue
Closed
opened 2026-03-22 14:13:32 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-03-22 14:13:32 -05:00
Owner
Copy Link

Originally created by @LilithElina on GitHub (Mar 10, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

I am currently testing the CalDAV integration via DAVx5 and tasks.org (and also jtx Board) on Android (stock and Graphene OS).
I'm aware that CalDAV integration is still in development.

When I create a task with subtasks in the Vikunja web interface it is flawlessly synchronised to both apps. If I do it the other way around, Vikunja struggles to interpret the data provided by the apps, the problems are identical when I try jtx Board or Tasks. Subtasks are partly shown independent of their parent, or under a parent named "DUMMY-UID-...". Here, each subtask gets a new parent with identical dummy ID. This is then also synced back to the Android apps. For Tasks, at least only the name of the parent task is changed, the subtasks still exist below it as intended.

Interestingly, adding a subtask to a parent created on Vikunja does not result in chaos, so it's easy to avoid the issues, but probably good to know for development.

Vikunja Version

v2.1.0-160-30fccfb0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Image

Image

Originally created by @LilithElina on GitHub (Mar 10, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description I am currently testing the CalDAV integration via DAVx5 and tasks.org (and also jtx Board) on Android (stock and Graphene OS). I'm aware that CalDAV integration is still in development. When I create a task with subtasks in the Vikunja web interface it is flawlessly synchronised to both apps. If I do it the other way around, Vikunja struggles to interpret the data provided by the apps, the problems are identical when I try jtx Board or Tasks. Subtasks are partly shown independent of their parent, or under a parent named "DUMMY-UID-...". Here, each subtask gets a new parent with identical dummy ID. This is then also synced back to the Android apps. For Tasks, at least only the name of the parent task is changed, the subtasks still exist below it as intended. Interestingly, adding a subtask to a parent created on Vikunja does not result in chaos, so it's easy to avoid the issues, but probably good to know for development. ### Vikunja Version v2.1.0-160-30fccfb0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots ![Image](https://github.com/user-attachments/assets/ae069bd8-944f-444f-ad82-e9a3613cf23f) ![Image](https://github.com/user-attachments/assets/21a87d11-4192-4ee3-9291-cbc538b9bfae)
GiteaMirror commented 2026-03-22 14:13:34 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 10, 2026):

Can you share the steps you did to create the broken subtask from the other app?

@kolaente commented on GitHub (Mar 10, 2026): Can you share the steps you did to create the broken subtask from the other app?
GiteaMirror commented 2026-03-22 14:13:34 -05:00
Author
Owner
Copy Link

@LilithElina commented on GitHub (Mar 10, 2026):

Sure! In Tasks I simply create a new task and add some subtasks:

Image

As soon as I sync, it changes in Vikunja:

Image

And also in Tasks:

Image

@LilithElina commented on GitHub (Mar 10, 2026): Sure! In Tasks I simply create a new task and add some subtasks: <img width="864" height="1939" alt="Image" src="https://github.com/user-attachments/assets/539e36e4-cb67-4f1d-a846-e182d797be56" /> As soon as I sync, it changes in Vikunja: <img width="864" height="534" alt="Image" src="https://github.com/user-attachments/assets/a504ec4a-d153-4222-9acc-c4702155fc0d" /> And also in Tasks: ![Image](https://github.com/user-attachments/assets/269786a0-8ba5-416d-9e21-8a722d4b829b)
GiteaMirror commented 2026-03-22 14:13:35 -05:00
Author
Owner
Copy Link

@LilithElina commented on GitHub (Mar 10, 2026):

Sorry for closing this.

@LilithElina commented on GitHub (Mar 10, 2026): Sorry for closing this.
GiteaMirror commented 2026-03-22 14:13:35 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 10, 2026):

Does this happen when you create a task, sync it (so that it shows up in Vikunja), then add the subtasks?

Which database are you using?

@kolaente commented on GitHub (Mar 10, 2026): Does this happen when you create a task, sync it (so that it shows up in Vikunja), then add the subtasks? Which database are you using?
GiteaMirror commented 2026-03-22 14:13:36 -05:00
Author
Owner
Copy Link

@LilithElina commented on GitHub (Mar 11, 2026):

That works!

I'm using the AdminForge instance and don't know which database is behind that, sorry.

@LilithElina commented on GitHub (Mar 11, 2026): That works! I'm using the AdminForge instance and don't know which database is behind that, sorry.
GiteaMirror commented 2026-03-22 14:13:37 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Mar 11, 2026):

This issue has been fixed in #2389, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Mar 11, 2026): This issue has been fixed in #2389, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
GiteaMirror commented 2026-03-22 14:13:37 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 11, 2026):

That works!

That confirms the fix from https://github.com/go-vikunja/vikunja/pull/2389 will work. Please check with the next unstable build (or on the demo)

@kolaente commented on GitHub (Mar 11, 2026): > That works! That confirms the fix from https://github.com/go-vikunja/vikunja/pull/2389 will work. Please check with the next unstable build (or on the demo)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2587
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?