Our Atlassian Jira Software connector is dedicated to manage single product within the bunch of Atlassian products which is ‘Jira Software’. As part of Jira Software connector protocol, we do not modify any Atlassian user accounts that does not have Jira software Product with them. All our actions are done on users with ‘Jira Software’ product.
We modify other Atlassian users as part of other Atlassian connectors. We use SCIM protocols to connect to your Atlassian instance using REST APIs.
Account in Jira
IDHub pulls all atlassian user account information in your Atlassian instance (Cloud or Server based). We pull only user with jira-software-user groups only which provides them with ‘Jira Software’ access.
User Account attribute we fetch includes (but not limited to):
- Email Address (As a unique identifier)
- First Name
- Last Name
- Job Title
Our customers can choose to fetch any other attributes apart from the above as per their individual needs. With our Attribute based Access Control (ABAC), you can decide which information will be used on new user creation and which ones on user modifications.
Entitlements in Jira
IDHub Jira Connector pulls 2 types of entitlement from Atlassian for provisioning and de-provisioning.
- Jira Projects (Along with Project roles)
- Atlassian Groups (Only with Jira Software product)
Employees of your organization can request for both Atlassian Groups and Jira Projects as needed.
Also as part of Jira Software connector, we establish connection with Atlassian to fetch all Jira Projects and their roles that can be assigned to an individual.
Users require to pick role(s) as desired while requesting for a project. These roles are very specific to the project and as designed by your project administrator. Some of the role examples are:
- Service Desk Customer
These roles can be custom created in Jira too and we will pull those custom roles as well on the next sync process for users to request from.
Upon completion of approvals based on request workflow defined by you on a particular project, the users will automatically get access to the requested project in the desired role by our automated fulfillment.
As part of Jira Connector, we also fetch Atlassian groups. We only fetch groups that has Jira Software product in it and ignore rest of the groups.
Upon completion of approvals based on request workflow defined by you on a particular group, the users will automatically get the group and the associated product and respective project/spaces in the desired role by our automated fulfillment.
Note: Requesting for a group will not cherry pick Jira software based project access via Atlassian group as that is Atlassian process to provision every product related accesses.
Support and Maintenance
IDHub provides out of the box connector issue support and timely maintenance as a standard quality guarantee for all of our customers having our Cloud solution. However, any customization made to existing connectors requires managed services support plan for support and maintenance.