Labels

AlreadyInOctane
76
Automated Tests
171
Backlog Planning
232
Business Rules
173
Dashboard Usability
240
Field Enhancements
288
Global Search
38
Manual Tests
351
Mobile Testing
7
Requirements
119
Shared Space Management
152
Team Backlog
206
Usability
1070
User Management
171
Top Voted Ideas: Last 30 Days
Allow to convert task to backlog item
17
Idea ID: 2875504

Create a new workspace with the customization of an existing one (same shared space)

Iulia Andreicut  
Status: Delivered

We now support an external solution to copy the customization of a workspace into a target one.

Shift - ALM Octane and ValueEdge migration tool can be downloaded from here https://marketplace.opentext.com/appdelivery/content/shift-alm-octane-and-valueedge-migration-tool

We encourage you to give it a try and share your feedback with us.

The current idea has been marked as 'Delivered' to notify the voters and users who commented on it about the solution.

If an embedded solution within the application is still needed, please vote for this new idea:

 Create a new workspace with the customization of an existing one in the same shared space - an embedded solution in the application 

See status update history

Provide means to create a new workspace with the customization of an existent one in the same shared space. The new workspace should copy from the original workspace the user defined fields, business rules, entity workflows, entity forms and email customization, lists.

  • Please have this feature up as soon as possible! manaually create 1-1 is very time consuming !!!!!!! We have 200 workspaces need to create 1 by 1. 

  • This will be a very good features to us as our organization is managing a large amount of projects in Octane.

  • will be very helpful if it can be copied to other spaces as well 

  • What happened to this functionality? while we create a new workspace, it should definitely hint to copy a new structure/template form a workspace (from shared space) or by default it created from the skeleton copy of the Space. it should also identify to copy the data/users too at the time of creation. since if we would like to clone a workspace, what options do we have now, rather travelling entire galaxy & hitting the dead end. I strongly vote for the cloning at workspace level. 

  • unfortunately, when we say "customization" you need to define what that means.
    like Frank i would like to be able to set some teams, some access, some Environment lists, programs, etc. as the template that I can use when handing out a new workspace, so that I do not have to manually align all of these values every time we deploy a new WS to another customer area.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.