Redmine

The lft and rgt value of copied issues look good to me. Could you explain more details?

sqlite> select id, subject, lft, rgt from issues where root_id = 21;
id          subject     lft         rgt
----------  ----------  ----------  ----------
21          issue0      1           6
22          subtask1    2           3
23          subtask2    4           5

Could you please give me a hint? We have the same Problem here.
Tried to rebuild the tree but do get

`connect': Access denied for user 'root'@'localhost' (using password: NO)

on a bitnami-based installation.

We have this issue (again) on a redmine 4.2 installation.
Maybe this has to be opened and addressed to someone who can fiddle out the underlying reason.

We observed this while copying a task with multy-level subtasks:

• Task A
  • Task A.a
    • Task A.a.1
    • Task A.a.2
  • Task A.b
    • Task A.b.1
    • Task A.b.2

If we copy this we get this:

• Task B
• Task B.a
  • Task B.a.1
  • Task B.a.2
• Task B.b
  • Task B.b.1
  • Task B.b.2

Task B.a is having Task B as a parent, but is only showing this when in edit-mode.

We decided to delete Task B and replace it by a "handmade" Task C.
Now we see even more strange behaviour:
Task B.a is showing two parrent Tasks: Task A and Task C
edit: this was a mistake on my side. Task B.a.1 is showing Task B.a and Task C as parrents, what ist totally correct.

Doing a rails runner "Issue.rebuild_tree!" -e production did not solve the situation.
The database-Field root_id still has the id of Task A, what leads to this strange behaviour.