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 reply
    1
  • Subscribers subscribers
    6
  • Views views
    237
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Synch of "access_granted" fields between 2 Octane workspace.

gbetbeder

Hello the community,

It seems not possible to map the "access_granted" field between 2 Octane workspaces, is it a normal behavior or is it due to my MF connect version 4.4.153?

In my case, I have one workspace inheriting requirements from another workspace and it would be very usefull to inherit this information as well as it is very important in term of securtity.

conf:

MF Connect 4.4.153 (to be updated soon :) )

ALM Octane: 16.0.200.101 (enterprise)

Jira: v8.20.5

Thanks

Guillaume

  • Verified Answer

    +1  

    I assume you are referring to the field "Data access categories" introduced in a recent release of Octane 16.

    This field is a special reference-type field - and the referred to type "data_visibility" is not a "normal" type within Octane (like release, work_item, requirement etc.).
    As MF Connect thus doesn't know about this special type - and cannot sync this special type - the field(s) that are referring to it, are also unavailable.

    You can create an Enhancement Request for this via Support or - if you think other customers will also vote for this - via Idea Exchange here on the MF Connect community.

    In general, MF Connect focuses on sync'ing user-facing data, not meta-data like access rights.

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.