tasks
Subtasks become main tasks on Nextcloud
Hello,
I am experiencing a synchronization issue between tasks.org and Nextcloud Tasks. Sometimes, subtasks created from tasks.org become main tasks on Nextcloud Tasks once synchronized. This does not happen in the reverse direction (subtasks created from Nextcloud Tasks).
This problem does not occur all the time. I am trying to identify the pattern that causes this bug, and if I find it, I will update this issue.
The synchronization is done with DAVx⁵.
If you need logs, could you please let me know how to provide them?
Thank you.
For me, this happens when moving tasks between lists - IE if I have a parent task (used as a 'category' - ie Car to-do, House to-do, etc) with subs in a master to-do list, and move one of the subtasks to a to-do today list, it becomes a main task, but I figured this is expected since I'm moving a single subtask and not the parent.
Also using Nextcloud+DAVx⁵
I've noticed that when I add a new subtask in tasks.org, it will not show up in Nextcloud. But if I modify a different subtask in either tasks.org or in Nextcloud and force a refresh, then the new subtask will show up in Nextcloud at the same time as the status of the other one changes.
I've noticed that when I add a new subtask in tasks.org, it will not show up in Nextcloud. But if I modify a different subtask in either tasks.org or in Nextcloud and force a refresh, then the new subtask will show up in Nextcloud at the same time as the status of the other one changes.
Tasks.org delays uploading changes until 1 minute after your last edit, or when the app is backgrounded. Can you try creating a new subtask, performing a swipe-to-refresh gesture, then refreshing Nextcloud?
Tasks.org delays uploading changes until 1 minute after your last edit, or when the app is backgrounded. Can you try creating a new subtask, performing a swipe-to-refresh gesture, then refreshing Nextcloud?
Hmmm, initial attempts are working as expected—the subtasks are properly created and reflected in Nextcloud. But I have the feeling that when I was writing this bug a few days ago I would have tried this. I was manually refreshing everything multiple times. If the unexpected behaviour happens again, I'll update.