RELATED IDEAS
Copy an existing workspace when creating a new workspace
When creating a new portfolio (product) line and multiple products (workspaces) in it, I need to ensure that all these new products are configured identically. The more complex and customized the configurations, the more error prone and tedious it is. It'd be great if I could, when adding a product, copy configurations, custom fields, release templates, etc. from another product. Ideally, it'd be great to keep all products in a product line in sync.
-
ADMIN RESPONSEMay 18, 2022
Create custom workspace templates
Standardize the way you set up new workspaces so teams follow the same approach. Create a template with predefined workflow statuses, custom fields, automations, and more. This update is available for customers on our Enterprise+ plan.
Checkout the blog post for more details.
I definitely support this for exactly the same reasons described above.
We'd even like to be able to copy work items from the spaces we copy so that when we're prototyping workflow, structure, or other process changes, we can prototype using an exact replica.
I agree that this is desperately needed. My product team would like to have a PDLC template that we can copy over to a new workspace for when we begin new products/projects, so then we can go through the Aha process without messing with our original template. I understand you can copy releases, but this can be time consuming and our PMs would benefit from being able to simply copy the workspace. Hope to see some momentum on this, thank you.
This is desperately needed. Thanks!