RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit A-I-8909 Ability to clone a workspace needed.
Clone a product/project space
Merged
To drive best practise within an organisation and for efficiency, it would be good to be able to clone an entire product/project space.
I would create a product template that has all the requirements for our best practise product management within Aha! that any new teams can clone to start their new product on.
This can also be used for marketing projects.
-
ADMIN RESPONSEJul 22, 2022
Thank you for your idea. This is not currently planned on our roadmap but we will continue to monitor customer feedback. In the meantime, we would suggest leveraging existing template options, such as for features and release phases. Additionally, it is possible to clone a release, so you can create a standard for different types of projects and clone it when you kick off a new project.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
© 2024 Aha! Labs Inc.•All rights reserved
This would be helpful for me to test new configurations in an existing workspace.
I have a workspace that is having some issues, it's a live workspace so I do not want to change things until I know that they will work as needed. If we could copy this workspace, do our changes and test that the new configuration will work, this would help a lot. The original workspace has lots of custom configurations and it will be a lot of work to reproduce it to test our config changes.
We need to copy a workspace with all it's contents for testing new configurations and new workflows.
Agreed! We have a repeatable approval process which is done through workspaces. Each new workspace has the same releases, features, models, etc. Ideally, I would love to copy a workspace with all of it's contents for this, but since that does not exist I am creating as many templates as possible.
Agree with all the below. We have separate product teams sharing the same product stack with identical and then separate requirements. We've been using tags but for scenario road mapping we needed a separation. Had to clone releases, lose initiatives etc and work independently..
This is a feature that is important when a product splinters into two independent products. I have this problem because two different product managers are working the products that come from 1 existing product. I need them to have independent spaces. Copying from one would solve this quickly with the PM's removing what doesn't apply versus having to review and copy.
This will help to create and deploy the system faster. Please get this implemented.
Hello,
this is an important feature since you do not provide a sandbox environment for testing the various integrations. The ability to test integrations before allowing others to use is a critical part of reducing the risk of adding third party tools into Aha.
I'd like to make this same request with a slight variation. It would be great to be able to clone a product and also specify elements that "universally" apply to said products. Therefore, these universal elements - when updated - could be refreshed across all applicable products.
Hi. Just submitted a similar request. Does not appear to be possible in Aha, yet. Likey to be implemented in the future?