GDPR (DSGVO) and Security for Jira for Server/Data Center: Version 1.16.0 Release Notes
We have implemented a new feature for the Data Cleaner module. It allows you to configure custom and user anonymized templates to skip already scanned content during the search/anonymization process. This means that when this feature is enabled, it compares previously scanned content with prepared to be scanned content and only new or modified issues will be processed, not the entire scope of issues.
Also, we have implemented the ability to restart the last task with exactly the same parameters (if this is possible).
There are a few limitations:
- The service user defined in the addon configuration should have “Browse projects” and “Edit issues” permissions for the projects that are affected. If the permissions are not present, the required properties will not be saved and the affected issues will be processed again and again.
- Some 3-rd party apps may update issue fields without producing an ISSUE_UPDATE event. In this case, Data Cleaner could skip even updated content. You can decide where to use this option to reduce scanning time and where it is important to check all the content, even if it was scanned previously.