Home | Connectors | Jira | Jira - OpenText Directory Services Integration and Automation
Data flow: OpenText Directory Services ? Jira
Synchronize employee and contractor identities from OpenText Directory Services into Jira to automatically create users, assign them to project groups, and map them to the correct roles based on department, location, or job function. This reduces manual onboarding effort for project administrators and ensures users receive access to the right boards, issues, and workflows on day one.
Business value: Faster onboarding, fewer access errors, and lower administrative overhead.
Data flow: OpenText Directory Services ? Jira
Use directory-managed groups to control access to Jira projects, issue types, and workflow permissions. For example, developers, QA analysts, product owners, and external vendors can be assigned different access levels automatically through directory group membership. When a user changes teams, access updates in Jira without manual intervention.
Business value: Stronger governance, consistent permission management, and reduced security risk.
Data flow: OpenText Directory Services ? Jira
When a user is disabled, removed from a group, or transferred in OpenText Directory Services, Jira access can be revoked automatically. This prevents former employees or contractors from retaining access to active projects, sensitive issue data, or release plans.
Business value: Improved security posture and reduced compliance exposure.
Data flow: OpenText Directory Services ? Jira
Synchronize organizational teams from OpenText Directory Services into Jira to support project board membership, component ownership, and notification schemes. For example, a directory group for ?Mobile Engineering? can be linked to a Jira board, ensuring the right users are included in sprint planning, issue assignment, and release communications.
Business value: Better alignment between organizational structure and delivery workflows.
Data flow: Bi-directional, with OpenText Directory Services as the source of identity and role data
Use directory attributes such as department, manager, or job role to route Jira issues to the correct approvers or assignees. For example, security-related tickets can be automatically assigned to the security team group, while change requests can be routed to managers in the relevant business unit. Jira can then reflect the current organizational role structure maintained in OpenText Directory Services.
Business value: Faster issue resolution and more accurate workflow routing.
Data flow: Jira ? OpenText Directory Services, with directory data used for reconciliation
Combine Jira project membership and permission data with OpenText Directory Services identity records to produce access reviews for audits and internal controls. Security teams can verify who has access to which Jira projects, whether access matches current employment status, and whether any orphaned accounts exist.
Business value: Easier compliance reporting and improved access governance.
Data flow: OpenText Directory Services ? Jira
For external contributors, create time-bound directory groups that automatically grant and later remove Jira access for specific projects. This is useful for implementation partners, QA vendors, or temporary development teams that need controlled access to backlogs, defects, and release tasks without permanent accounts.
Business value: Controlled third-party access and reduced manual cleanup.
Data flow: OpenText Directory Services ? Jira
When employees move between departments or teams, update their Jira group memberships and project permissions automatically based on the new directory assignment. This helps preserve continuity in active sprints, issue ownership, and notification subscriptions while ensuring users only retain access relevant to their current role.
Business value: Reduced disruption during reorganizations and cleaner access alignment.