Templates (page template, work item templates, work item types etc.) are related to projects, which is fine.
However, most of the time I need to keep consistency not only in a project but in the complete workspace. So the request is to be able to define templates on a workspace level or at least be able to copy templates between projects.
As far as as I understand your blog, a “project-as-code” with import functionality in the plane UI could also be a solution for that scenario.
Project templates and Page templates are already at the workspace level, so you can use them across all projects.
Work item templates are project-level because work items themselves are project-specific. Each project can have its own work item types, epics, states, etc., so templates are defined at that level to match the project’s configuration.
With Plane Compose and project templates, you should be able to duplicate projects though. It’s currently limited to cycles, modules, work items, views, and work item types - but it might help with your use case.
Work item templates are project-level because work items themselves are project-specific.
You are right if you think about project management of diverse projects. But what I have is an organizational unit, which is doing internal projects. These projects all (must) have the same structure.
With Plane Compose and project templates, you should be able to duplicate projects though. It’s currently limited to cycles, modules, work items, views, and work item types - but it might help with your use case.
Looking forward to that. I hope it is available via the plane UI.