Defect #15581
Updated by Toshi MARUYAMA over 10 years ago
We currently have a task with around 90+ sub tasks on our hosted redmine server. The task and all of the subtasks are attached. 2013_11_25_13_09_05_Group_6496.jpg 2013_11_25_13_09_40_Group_6496.jpg The problem started when we recently added two tasks to the existing tree, 7062 and 7063. Both of these tasks are already created, and have their parent tasks set afterward. After adding both 7062 and 7063 to the parent 6512, we got the lower portion of the list (below task 6515) cut off and some tasks are missing from the list: !2013_11_25_13_45_41_Group_6496.jpg! Also if we open the task 6515, we can see this parent tree structure: !2013_11_25_13_47_10_Group_6515.jpg! We have checked that all all the tasks have the correct parent task assigned. We did a further investigation into the database table and found these facts: * Before adding 7062 and 7063 to parent task 6512: | Task # | lft | rgt | | 6496 | 1 | 180 | | 6512 | 106 | 111| |6515 | 130 | 179 | | 7062 | 1 | 2 | | 7063 | 1 | 2 | * After adding 7062 and 7063 to parent 6512: | Task # | lft | rgt | | 6496 | 1 | 114 | | 6512 | 106 | 115| | 6515 | 134 | 113 | | 7062 | 111 | 112 | | 7063 | 113 | 114 | * To fix the problem, we had to manually changed the rgt values to: | Task # | lft | rgt | | 6496 | 1 | *184* | | 6512 | 106 | 115| | 6515 | 134 | *183* | | 7062 | 111 | 112 | | 7063 | 113 | 114 | Seems when setting parent task of 7062 and 7063 to 6512, the wrong values of rgt are updated to 6496 and 6515. We can reproduce this problem again by removing parent task of 7062 and 7063 and assigned them back 6512. We think the problem is similar to #11011 http://www.redmine.org/issues/11011 The redmine version that we are using is: !2013_11_25_13_57_19_Information.jpg!