Hey guys,
By default - our gantt filters out inactive tasks using taskStore.filter(...)
When a task is filtered out, you can see it missing in the wbs structure (this is good).
However when a task is added below the task immediately preceding the inactive (in this example, we added a successor to 2.1.1.1) the new task's parentIndex overwrites the inactive task, and then all tasks except the one filtered out are shuffled up. You'll notice in the below no update for task 2.1.1.2, and the parentIndex for 2.1.1.3 (the new task) doesn't match it's wbs.
When we send our tasks down from the server, we use the parentIndex and parentId properties on the tasks to build the tree, and this causes a conflict as now two tasks have the same parentId and parentIndex - which means the inactive one doesn't come down the wire.
Not sure exactly where the problem lies here. Are we filtering incorrectly? Is this an issue with inactive tasks? Or with the update logic using the filtered store?
Any advice would be appreciated.
Thanks
Chris