Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.

Copy Workspace

Idea ID 1673716

Copy Workspace

Should be possible to:

Copy workspace to another location..

  • Isolated workspace to other Isolated workspace
  • Shared workspace to other Isolated workspace


  • Use this for testing out functionality with needed data
  • When a workspace within a shared workspace has the need for doing more changes which cannot be done within the shared workspace limitation


Micro Focus Expert
Micro Focus Expert


If you want to push the same customizations and data (requirements, tests, defects, users, ...) into Octane workspaces you could also try the ALM Content Packs: 

I'd suggest you try the CCPA version since it contains much less data than the GDPR version. You'd need to replace the regulatory and demo content with your own data.

Since this workaround is much more work than a simple export / import this is usually only feasible if you want to rollout a template many times.





Our use case is that we use a single isolated space for all of our workspaces. Our projects serve clients. When the client project is over and a new client project begins a new workspace is created. Ideally the new workspace could be built with a preconfigured template so that our projects don't have to set up the same configuration over and over and over again. We have no interest in copying data only configuration.

I understand that shared spaces has functionality to support this, however due to the multi-tenancy of our Octane instance we deemed shared spaces not suitable for our security, maintenance, and provisioning needs.


Commander Commander

We have a business need to Copy/migrate Workspaces from one space to another.

Business reason:

When we started we choose a topology design based on what we thought would work here, we have since thrown it out. But cannot rearrange our workspace/Space’s to match our new Topology, I would have thought this would be common for new implantations of octane in complex environments.

We have a Space that we use for training & Pilots, a primary Space and various isolate spaces.

Some of our Pilots have decided to go to production with their use of Octane. But as our Primary Space already has multiple Workspace in it We have no way of migrating the “Team C” Workspace from our “Training& Pilot” Space to our Primary space.

We also have Workspace that get created in isolated Spaces due to process or security reasons. In the case of a tender evaluation, once the tender is chosen the Workspace no longer needs to be in the Isolated Space and need to be able to work with the other spaces in our primary space. We can foresee this will be needed multiple times a year.

Technical information:

We design our space to minimize maintains of Octane for our small team of Administrators/support staff. As so a lot of information is defined and maintained at the space level (shared Application modules, Shared releases, etc).

As workspace do not contain the “space shared entities” exporting a workspace will not work for migration to a new workspace. Relationships will be broken or misaligned.

We need a solution where in the Admin manage workspaces screen I can select a workspace and then start a migrate to Another/new space option. This could be another button alongside these buttons “add workspace/delete workspace/Edit workspace” or an option in the “Edit workspace” dialog.


This Button would triggers a process that checks the shared entities in both spaces. Then presents that admin with a list of all shared entities, with the follow selection options for each item:

  • Source WS/Space Shared entity created as a Workspace level Entity
  • Map Source WS/Space Shared entity to an EXISTING WS/Space shared entities in the new WS/Space.
  • Source WS/Space Shared entity to be created as NEW spaced space entity in new WS/Space.

This is becoming a very urgent need for our site.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.