Table of contents:
Overview
Only Jira Administrators and Jira System Administrators are able to use GDPR 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 GDPR app will use to apply changes to affected issues. Add this user to the 'project administrators' role in all projects you want to synchronize.
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 users and groups
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
Delete All Worklogs
Read more about permissions in Jira https://confluence.atlassian.com/jirakb/jira-permissions-general-overview-625902332.html
Main settings
URL: https://%hostname%/secure/admin/actonic-gdpr-configuration.jspa
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 updates 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. |
Announcement performance - Show new announcements in real-time (optional) | 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 | If checked, tracks all issue view events through browser and REST calls. Assists with investigating of user's activity and if a user’s account was hacked or compromised, it allows you to find all the content that this user had access to and which was viewed. 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 - Purge Issue access log after (required) | 30 | Access statistics will be removed automatically in X days after collecting. |
Restrict access to GDPR and Security - Select group (optional) | empty | You can define which users will be able to use GDPR functions. Regardless of the selected group, only Jira Administrators and Jira System Administrators will be able to use GDPR functions. |
Stored Data
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.