Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error moving task with subtasks from one projet to another #1496

Open
BPier opened this issue Dec 19, 2024 · 2 comments
Open

Error moving task with subtasks from one projet to another #1496

BPier opened this issue Dec 19, 2024 · 2 comments

Comments

@BPier
Copy link

BPier commented Dec 19, 2024

Describe the bug
When moving a tasks that contains subtasks from project A to project B, the parent task and the subtasks are moved in Planify. In Nextcloud only the parent task is moved to project B and the subtasks stay in Project A.

At the next synchronisation the subtask is deleted.

To Reproduce
Steps to reproduce the behavior:

  • In Planify, in an instance synchronized with Nexcloud create 2 projects: Project A and Project B
  • In Project A, Create a parent task ("Parent") with a subtask ("Child 1")
  • Make sure that the tasks are synchronised in Nextcloud
  • in Planify move the task "Parent" to project B
    • In Planify -> Now the task "Parent" and the subtask "Child 1" is located in Project B
    • in Nextcloud -> Now the task "Parent" is located in Project B and the task "Child 1" is now alone in Project A
  • Click on the wheel to force the synchronisation in Planify
  • Now the task Child 1 has been removed from the parent in planify
  • From now on the behavior is a bit chaotic, the task might appear or disapear each refresh in nextcloud

Expected behavior
The tasks AND the subtasks should be moved in Planify AND Nextcloud

Desktop (please complete the following information):

  • OS or DE: NixOS, KDE Plasma
  • Version: NixOS unstable, Nextcloud version 30.0.2 , Planify 4.11.6
@janvlug
Copy link

janvlug commented Dec 24, 2024

Slightly related to #1457 and #2700.

@EricDuminil
Copy link

EricDuminil commented Jan 26, 2025

I can confirm this bug. Which means I basically cannot use Planify to organize and sort my Nextcloud tasks: as soon as I define a sub-task in my Inbox project, it's dangerous to move the task to another project, since I will end up with inconsistent states on the server and app.

This bug might not appear when moving from the local Inbox, since it doesn't get synced with any server.

EDIT:

for what it's worth:

in Planify move the task "Parent" to project B

In Planify -> Now the task "Parent" and the subtask "Child 1" is located in Project B
in Nextcloud -> Now the task "Parent" is located in Project B and the task "Child 1" is now alone in Project A

In Nextcloud, "Child 1" was both a top-level task in Project A, and a Sub-Task in Project B. Removing it in Project A,also removed it in Project B.
Moving it from Project A to Project B resulted in "Child 1" being a top-level task in Project B.
In both cases, state in Planify doesn't mirror the state in Nextcloud, and it's not clear how to fix the problem afterwards.

Just in case it could help, NextCloud tasks code when moving a Task seems to be here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants