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

Reason

  • 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

 

23 Comments
Lieutenant
Lieutenant

Without the ability to copy a workspace we are unable to spin off a new project based on an existing model - similar to a template or a base project with standard workflow and lists like we do in ALM.

Teams are stuck adding "creative" names to an already overloaded and outdated workspaces so they don't lose the configurations and customization built.  

Micro Focus Expert
Micro Focus Expert

Thank you for your feedback

This feature is requested by many customers and planned with high priority.

We are planning to provide an ability to export a workspace with all the data and import it to the same space (which will enable copy & backup/restore at workspace level).

no ETA yet.

 

Regards,

Sigal

Captain
Captain

Yes! When building workspace import/export function, please consider making it configurable to indicate if you just want to export settings, or settings + data, exclude users or include users, etc.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted

Status change to Accepted. No ETA yet.

Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

Hello! Are there any updates on this feature? Possible ETA/realse date? Thank you in advance!

Micro Focus Expert
Micro Focus Expert

Hi @Eugene Russkikh 

Can you specify what are the use cases for you to use Copy workspace?

As this is a very complicated functionality, it will take some time to implement and i want to understand the main use cases of copy workspace from you side so that maybe we can suggest you with temporary solutions.

Regards,

Sigal

Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

Hello @Sigal_Ishay ,

 

This feature would be ideal for testing purposes in my case. If one could duplicate a workspace, then the original data would stay intact.

 

Did I understand correctly, there is no ETA yet? Thank you!

 

Best,

Eugene

 

Commodore Commodore
Commodore

@Sigal_Ishay @Adi Kimhi 

 

Thanks team for the information.

 

As a use case, what we would like is the ability to copy or move a workspace from one Shared Space to another Shared Space.

Please let me know if this can be done at the moment or if it is planned?

adding FYI @Alex_J @RobertHay 

Micro Focus Expert
Micro Focus Expert

Hi ,

This functionality is not available in Octane and with no ETA yet.

The reason i asked to specify the use cases is to understand whether we can suggest alternatives to answer your needs.

@Eugene Russkikh  - If this is required for testing needs, such as creation of staging environment, i guess you can use the built-in solution we have recently added to Export/Import space (with all its workspaces data). You can use this option to create a staging environment to test the workspace you want to test within its shared space.

hope that should answer the need.

@SF1 

Moving a workspace from one shared space to another is very complicated as it will conflict with the new shared space customization which is not aligned with the workspace customization and might cause conflicts and data issues.

we do plan to provide a way to export/import a workspace to the same shared space (mainly for backup restore purposes) but not to a different shared space.

 

Regards,

Sigal

 

Captain Captain
Captain

@Sigal_Ishay 

If the current import tool were extended to do initial customization checks prior to importing the data, this might assist in providing functionality where there are either no, or the same customization applied to both target and destination.

Another way to achieve this would be to export and customization for that workspace and apply it to the exported workspace as a 'workspace level' customization as a part of the export process.

You could also warn that the target spaces' customization will be applied to the workspace when merging the data into the new space. You could then run an update tool over the workspace to uplift the contained metadata to align with the new shared space. Similar to the way you update the DB schema during the upgrade process.

 

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.