What is inside the Audit Report
Overview
It is possible to download the Audit Report in Excel format after the scanning has completed.
The report helps to answer the following questions
Who has access to the project?
What kind of access the user have?
How come the user has access to the project?
This page explains the information provided in the Audit Report.
Organization
The report will list down all the users for all the selected projects. If the user has some permissions for the project, there will be a row added in the report. If the user does not have any permissions for the project, it will not be included in the project.
i.e. If a user has access to 5 projects. There will be 5 rows for that user.
To avoid cluttering the report, deactivated users are excluded from the report.
Columns
The table below will help you understand what each field correspond to in the Audit Report.
Grouping | Field | Description |
---|---|---|
Project information | Project Category | The category of the project |
Project Type | The type of project. Possible values are:
| |
Project Key | The key of the project | |
Project Name | The name of the project | |
Project Lead Name | The name of the Project Lead | |
User Information | User Name | The user name of the user who has entry in this project. |
Display Name | The display name of the user who has entry in this project | |
User Email | The email address | |
Permissions | Administer | User can administer the Jira project |
Read (Browse) | User can browse the Jira project | |
Write | If user has any of the Write permissions below, it will be set to Yes. Blank otherwise. | |
Write (Create Issue) | Create Issues | |
Write (Edit Issues) | Edit Issues | |
Write (Delete Issues) | Delete Issues | |
Write (Create Attachments) | Create Attachments | |
Write (Delete Own Attachments) | Delete All Attachments | |
Write (Delete All Attachments) | Delete Own Attachments | |
Write (Add Comments) | Add Comments | |
Write (Delete Own Comments) | Delete All Comments | |
Write (Delete All Comments) | Delete Own Comments |
Permissions JSON Values
For the Permissions fields, they will populated with a JSON string to explain why the user got the permission
Values | Example | What it means | To revoke |
---|---|---|---|
User does not have this permission | |||
{"app_access" : "any_logged_in_user"} | {"app_access" : "any_logged_in_user"} | User has this permission because he can log in |
|
{"app_access" : application} | {"app_access" : "jira-software"} | User has this permission because he has been assigned a Jira-software license |
|
{"RoleUser_ProjectRole" : "user"} | {"RoleUser_Administrators" : "victor"} | The user victor has been added as Administrators role within the project |
|
{"RoleGroup_ProjectRole" : "group"} | {"RoleGroup_Administrators" : "jira-administrators"} | The group jira-administrators has been added as Administrators role within the project |
|
{"group": "group"} | {"group": "jira-administrators"} | User has this permission because he is a member of the jira-administrators group which is configured within the permission scheme |
|
{"user" : "user"} | {"user" : "victor"} | User victor has been explicitly given this permission via the permission scheme |
|
In summary, blank means no permission. Otherwise, it means the user has permission.
If you want to switch to a true/false setup, you can use the Excel isBlank() function.