Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    12
  • Views views
    79
  • Users 0 members are here
Related
Options

Migrating PPM and Octane Agile Integration Request Type field Mappings configuration.

puthar

Good day,

Our customer made the following comment because I had to manually setup the Octane Request Field mappings: "We (and all software products) are pushing for CI/CD and automated deployment.  It is concerning that PPM does not support this"

I am not sure if this is a possiblity that OpenText will consider to enable the migration of Integration componenets from one PPM enevironment to another through the Deployement Management.

Please can you provide me a response which I can use for feedback to the customer?

Regards,

Alfred Puth

iOCO: Senior PPM Consultant

  • Verified Answer

    +1  

    Hi Alfred,

    We implementing migration of agile configurations a long time ago. If you run kMigratorExtract.sh in PPM, you'll see that Agile Configurations (which includes field mappings) is listed as entity ID 9900: 

    However, the reason we haven't pushed this further (as an official DpM PPM Migration Object Type) is that Migrating an Agile Configuraion is completely impractical in real life: A PPM Development environment will never be directly integrated with the Production Octane environment (or Jira, or any other Agile tool). As such, there's no guarantee that the IDs of mapped entities that have been mapped in Dev will remain the same when looking at Production. In other words, if you just migrate a Dev Mapping to Production, the results are completely unpredictable. Migration Agile configuration is irrelevant at best, definitely not predictable, and possibly dangerous.

    So, feel free to try it if you are confident that the PPM dev environment is recently refreshed from Prod (to ensure that IDs of request types & fields are the same) and if you integrate PPM Dev with Octane Prod - or are sure that the IDs of configuration items in Octane Prod & Devs environemnt will be the same - which may not be the case if you have an Octane Workspace for Dev and one for Prod, as is the usual practice. Your call!

  • 0 in reply to   

    Thanks Etienne.

    My first thoughts as well that mapping keys and IDs will cause issue because of the different Octane environments.

    Regards,

    Alfred Puth

    iOCO: Senior PPM Consultant

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.