Labels

Administration
73
ALM Connector
26
AlreadyInOctane
2
Audit-Reporting
16
Configuration
64
Connector Updates
26
New Connectors
17
Octane Connector
21
Sync Behavior
40
Type Rules
11
Usability
81
Idea ID: 2871097

Goodbye User Maps! Octane_Full_Name should be implemented as 4th Octane Connector User Representation option

davidvince
Status: Under Consideration

Advantage: For many users there is no need to create a user map anymore.

Hello all,

we would like to have the Octane connector with another user representation: "octane_full_name". Currently there are email, name and full_name. The latter (full_name) is a formed value of first and last name (we've checked it). Say MF Connect makes the Full_name currently so: First Name + " " + Last Name. Unfortunately, in our AD, the combination of first and last name are not the same as the display name. The display name contains special characters, whereas the first name and last name do not.

We map the DisplayName field in Octane with the Full Name field (LDAP Server Settings). However, this field is not provided in MF Connect. If the field existed, the user in Jira (also DisplayName) would exactly match the one in Octane. User mapping would no longer be necessary.

We have dozens of Data Sources and over thousands of users. The user mapping is not perfect, even with .bat-File automation.

  •  

    Several approaches for minimizing the need for MF Connect User Maps are currently under consideration - currently (subject to change at any time) as "SHOULD HAVE" for the next release of MF Connect and "MUST HAVE" for the release(s) after that).

    The scenario here is one of them - but the not among the TOP items of the list of user mapping improvements (as it requires changes in the product Octane, as well - and it is not generally applicable to all or even most customer scenarios).

    Common to all potential user mapping improvements is the goal to reduce the need for User Maps that need to be maintained.

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.