App configuration
Table of contents:
Overview
Only Jira Administrators and Jira System Administrators are able to use Data Protection and Security Toolkit app functions.
It is strictly required to configure the app before the first usage. Firstly, you need to create a dedicated Jira user (“Service User”) that the Data Protection and Security Toolkit will use to apply changes to affected content. Grant this user All the permissions in all projects you want to clean-up (anonymize).
It is not possible to use most of the app’s functions without the “Service User” defined! Please select a technical user with the maximum permissions in the application and all the projects:
Read more about permissions in Jira: JIRA Permissions General Overview | Jira | Atlassian Documentation
Main settings
Option | Default value | Description |
|---|---|---|
Service User (required) | empty | A technical user with the maximum permissions in the application and all the projects. Will be used in Data Cleaner, Recurring Tasks, User Anonymizer modules as the user on behalf of which all search, anonymization, and update processes will be executed. May be defined as a real user, but it could have a side effect with unwanted notifications and filtering. |
Pagination configuration – Rows per page (required) | 20 | Quantity of the elements per page in all the modules. If you have more elements, they will be stored on pages 2, 3, etc. with pagination. |
Announcements performance | Show new announcements in real-time | By checking this option, newly created announcements will be shown in real-time, and may produce a lot of requests on high-load servers |
Issue access statistics tracking – Purge Issue access log after (required) | 30 | Access statistics will be removed automatically in X days after collecting. |
Restrict access to Data Protection and Security Toolkit – Select group (optional) | empty | You can define which users will be able to use Data Protection and Security Toolkit functions. Regardless of the selected group, only Jira Administrators and Jira System Administrators will be able to use Data Protection and Security Toolkit functions. |
Stored data
Option | Default value | Description |
|---|---|---|
Announcements History | empty | Shows total number of all announcement/notifications history entries. May contain personal data of users. Can be cleared from here. |
Data Cleaner History | empty | Shows total number of all search/anonymization history entries. May contain personal data of users. Can be cleared from here. |
Recurring tasks | empty | Shows total number of all Recurring Tasks history entries. Doesn’t contain personal data of users. Can be cleared from here. |
Access Statistics History | empty | Shows total number of all viewed tickets history entries. May contain personal data of users. Can be cleared from here. |
Performance - Threads and Nodes
To make our application perform faster, you can use the option of choosing the exact Node and number of Threads this application will run on.
The speed and configuration mostly depends on your server. If number of chosen threads is higher than what’s available, application will not preform faster, but use available resources.
Please be aware:
If there is more than ONE node on the server, and that node is chosen, what number of threads user specifies to be used from that node, will 100% be used. Meaning that the load can go up to 100% depending on the configuration.
If there is ONLY one node, to use all the threads, a module called “Essential protection for Data Center” can be disabled, so ALL threads from that ONE node will be used.
This option is risky, because it will overload the only node of the server and may cause issues. Please read the description of a module before disabling it.
Other performance related configuration
In order to use this application with maximum available performance, please refer to the point above regarding Threads and Nodes.
Also, please keep in mind the following:
Number of custom fields will have an effect on the application performance, please use the recommended amount shared by Atlassian - https://confluence.atlassian.com/enterprise/managing-number-of-custom-fields-in-jira-data-center-1488597907.html#:~:text=Still%20need%20help?,What%27s%20the%20recommendation?
In case of thousands of custom fields, the search/anonymization process may be longer compared to a standard run
Limit the scope to only what is needed
Limit the objects to only what is needed
During Data Cleaner template creation, please check:
Try to skip already scanned content - this feature will make the app perform faster for the consecutive runs with the same template
Exclude fields that are not added to any screen of the issue project - this feature will exclude custom fields that are not part of the project in the scope