Table of contents:
...
| Info |
|---|
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 issuescontent. Add Grant this user to the 'project administrators' role All the permissions in all projects you want to clean-up (anonymize).
| Note |
|---|
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:
Browse tickets Assign Issues Delete Issues Edit Issues Modify Reporter Schedule Issues Set Issue Security Transition Issues Manage Watchers Add Comments Delete All Comments Delete All Attachments |
...
Read more about space permissions in Jira
...
Main settings
URL: https://%hostname%/secure/admin/actonic-gdpr-configuration.jspa
...
: 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 |
checked
If checked, new announcements and notifications will be shown on all user screens without page reload or any other actions. May produce redundant requests from client to server on instances with 10000+ users. Uncheck if you see any effect on performance and multiple requests in log files.
Issue access statistics tracking - Enable Issue access statistics tracking (optional)
not checked
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 |
...
You can get an overview of all the stored data and cleanup it instantly. The deletion of these data is permanent and irreversible. After successful deletion, you will not be able to view the previous 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. |