Atlassian Data Processing

Zluri fetches the list of users and licenses from Atlassian Admin, Jira & Conlfuence. This article explains how you can validate the data presented in Zluri.

 

How Zluri fetches the data:

Zluri calls the following APIs to fetch the data.

 

 

 

Status & License Mapping:

For Jira: Zluri processes the users from the Jira API with accountType : 'Atlassian' and active: True. Out of which the Zluri matches the users coming from Atlassian Admin with accountId. 

 

  1. User present in Atlassian Admin with Product Access = Jira Software, User Application Status = Active, Licenses mapped.

  2. User present in Atlassian Admin without Product Access = Jira Software, User Application = Inactive, License not mapped.

  3. Users not present in Atlassian Admin, User application status = Active, License not mapped. There could be some unmapped users out of this, Please map the users to email ids get the exact user count.

 

 

For Confluence: Zluri processes the users from the Jira API with accountType : 'Atlassian' and active: True. Out of which the Zluri matches the users coming from Atlassian Admin with accountId. 

 

  1. User present in Atlassian Admin with Product Access = Confluence, User Application Status = Active, Licenses mapped.

  2. User present in Atlassian Admin without Product Access = Confluence, User Application = Inactive, License not mapped.

  3. Users not present in Atlassian Admin, User application status = Confluence, License not mapped. There could be some unmapped users out of this, Please map the users to email ids get the exact user count.

How to validate the data:

 

You can login to your atlassian admin account check for the billed users.

 

 

To export the list of users, You can download the list of users from product access = Jira Software.


 

For confluence, You can check the similar details on same pages.

Can’t find what you are looking for? Let us help you!

Atlassian Data Processing

Modified on Wed, 15 Mar 2023 at 02:23 AM

Zluri fetches the list of users and licenses from Atlassian Admin, Jira & Conlfuence. This article explains how you can validate the data presented in Zluri.

 

How Zluri fetches the data:

Zluri calls the following APIs to fetch the data.

 

 

 

Status & License Mapping:

For Jira: Zluri processes the users from the Jira API with accountType : 'Atlassian' and active: True. Out of which the Zluri matches the users coming from Atlassian Admin with accountId. 

 

  1. User present in Atlassian Admin with Product Access = Jira Software, User Application Status = Active, Licenses mapped.

  2. User present in Atlassian Admin without Product Access = Jira Software, User Application = Inactive, License not mapped.

  3. Users not present in Atlassian Admin, User application status = Active, License not mapped. There could be some unmapped users out of this, Please map the users to email ids get the exact user count.

 

 

For Confluence: Zluri processes the users from the Jira API with accountType : 'Atlassian' and active: True. Out of which the Zluri matches the users coming from Atlassian Admin with accountId. 

 

  1. User present in Atlassian Admin with Product Access = Confluence, User Application Status = Active, Licenses mapped.

  2. User present in Atlassian Admin without Product Access = Confluence, User Application = Inactive, License not mapped.

  3. Users not present in Atlassian Admin, User application status = Confluence, License not mapped. There could be some unmapped users out of this, Please map the users to email ids get the exact user count.

How to validate the data:

 

You can login to your atlassian admin account check for the billed users.

 

 

To export the list of users, You can download the list of users from product access = Jira Software.


 

For confluence, You can check the similar details on same pages.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article