With multiple workspaces, you can set up mabl for independent teams within your organization. Depending on your team’s workflow, you may want to provide new workspaces with a set of starter tests or transfer ownership of tests that were previously managed elsewhere. You can accomplish this through a workspace copy.
Reach out to the mabl team
To copy tests between workspaces, please reach out to your customer success manager (CSM) or technical account manager (TAM) from mabl for assistance. Workspace copy does not migrate over all components and has limited filtering capabilities. (See limitations for more details.)
If you don’t know who your CSM or TAM is, reach out to cs@mabl.com.
How it works
Workspace copy can migrate the following components from a source workspace to a destination workspace:
- Tests
- Flows
- Snippets
- DataTables
- File uploads
Workspace copy supports filters to limit which tests are migrated. When used, only DataTables and file uploads that are associated with the included tests are migrated to the destination workspace. However, there are no supported filters for restricting the migration of flows and snippets. Workspace copy migrates all flows and snippets from the source workspace to the destination workspace.
Limitations
Workspace copy cannot migrate the following components from a source workspace to a destination workspace:
- Branching and version information
- Plans
- Applications
- Environments
- Credentials
- Resource group settings
- Database connections
- Permanent mabl Mailbox email addresses
- Mobile build files
There is also no ability to limit which flows and snippets are migrated. All flows and snippets are copied from the source workspace to the destination workspace.
If any of the previous limitations are important for your team, please let us know in the mabl Product Portal.