Not sure if this is really viable given the sheer number of different use-cases, but I wondered if there may be a way to potentially do some of the heavy lifting at least for creating a new whiteboard/mindmap and moving in all tasks matching a certain criteria.

It may be best if I explain using a sample use-case.

Scenario:

We currently have a "content plan" list for each client. Within that list, it as a number of different tasks with each task representing an individual piece of content.

Within the task we have a custom field which tells us which content cluster/topic the content belongs to

What I would like to be able to do is setup a whiteboard (for this example - let's say a bubble map which shows how various clusters of content are all related to each other)

Current situation/problem:

I had a feeling (I may be wrong) that the legacy version of whiteboard presented an option to auto-create a board based on existing tasks. However, I've just tried to setup a new whiteboard, so perhaps I'm wrong?

Either way, currently it looks like in order to build the bubble map, I have to manually add each task, and then form relationships between them.

Desired solution:

Currently, as tasks are sometime nested, and/or share a common custom field (e.g. topic), it may be possible to automate some of the initial creation of the bubble chart.

For example, let's say we have a "topic" set of "Recipes", and we have the following tasks already in existence, it would create "Recipes" as the central node, and each of the following as a node surrounding it 1 node point away from the centre in each case.

* Chocolate Eclairs

* Victoria Sponge cake

* Chocolate Brownie

Now, let's imagine that "Chocolate Brownie" has a subtask to create a dedicated recipe page for "Gluten free chocolate brownies". As it's a subtask, it would be good if it automatically created it as a sub-node of "Chocolate brownie".

I hope that makes sense?

Complexity considerations:

One example of where I appreciate how complex this could be, is, for example, how you might create a "Gluten free" node which subsequently links to tasks which are contained within other nodes already. The answer may come with simply manually creating a new "task" for a page which lists all "Gluten Free" recipes, and then forming a relationship between the tasks..... or perhaps adding an additional custom field category. So I do appreciate this could be a nightmare to implement in a way which works for all users across all use-cases.

Similarly, I appreciate the approach and logic would need to be different for each Whiteboard approach. For example, trying to automate population of the "process flow" template might only work for those with sub-tasks, and the user might therefore need to manually arrange and connect the various tasks. However, even the fact that the tasks are automatically added to the whiteboard might be helpful in some cases as it reduces the risk of something potentially being missed.

Adding a filter for what tasks are auto-imported would help reduce the risk of the whiteboard becoming cluttered from the outset; especially if you can import in batches

I hope the above all makes sense?