[Offer] Subtasks in a task

[Paul_Danyliuk]

Just in case anyone still wonders. This example contains a doc where any level of task/subtask nesting is possible (and as an addition, it’s visualized as a tree map):

Mind map (tree chart) implementation (!)

Okay, here it is. I made a mind map (actually a tree chart, sorry for the clickbait) implementation using the SVG capability I discovered last decade (ba-dum-tss) Best viewed in new tab. And yeah, it’s dynamic. Play around: turn off nodes, change parents, reorder rows, add new ones. [ezgif.com-optimize (62)] There are definitely bugs with the implementation, e.g. the chart may act funny when you reorder rows. Bug fixed, feel free to reorder now. And subscribe to codatricks.com if you have…

The idea is to specify a parent for each task. Feel free to use the above document as a template (copy the DB Items table and delete the columns responsible for tree map node position calculations).

Here’s how to limit the selection of parents to only valid ones, so that you don’t accidentally make a parent of a task that is already a sub-task of this task:

Prevent circular dependencies when adding child-parent relationships

Sometimes there’s a need to build an object hierarchy, e.g. tasks with sub-tasks with sub-sub-tasks etc, with indefinite nesting. To implement this, you’ll add a lookup column Parent to your table, pointing to the same table. However, if you don’t filter the options for selecting a parent, you risk running into a circular dependency and select a parent row that is already a descendant. To prevent this and narrow down parent choices, do the following: Construct each item’s path: If( thisRow…

This is already implemented in the above doc.