The behaviour you describe is to be expected.
If you clone an entity, you do not automatically clone related entities.
I can understand why you might expect it, but because Fibery workspace relations can become more complex than your example, making the ideal rules for which linked entities should be cloned and which shouldn’t is not easy.
I get that duplicating an entity can be complex, but I guess I’m used to vanilla copy/paste functions that will duplicate a “template” in its entirety.
On the other hand…while it looks like automation may require a little bit of setup, it seems to have all the functionality to accomplish what I need. I’ll give it a shot!
@Chr1sG I looked at the automation solution, but I have some heartburn over how it works - by creating a persistent relationship between the template and projects:
changing a project category triggers the automation and adds new tasks
adding a new task to a template adds that task to existing projects (yikes), but…
bc the trigger is on the task template add, the task contents, which are updated after the task template record is created, don’t get updated (but I see the code to copy contents)
deleting a task template doesn’t have any effect on existing project tasks (a good thing)
I can see where downstream maintenance on either/both a project and template could get a bit tricky.
So, I’ll pass on this approach - but is there an automation that does not rely on a persistent category-project relationship - eg. click a button and the automation simply copies a project template (in its entirety) with no residual relationship once the new project is added?