Installing the app

The app is available on the Atlassian Marketplace. To install the app, log in as a system administrator and navigate to the app management in the administration console (choose Cog icon > Apps at top right of the screen or use the keyboard shortcut: press 'gg' then type 'Find New Apps'). In the menu on the left, click the “Find New Apps” link. Search for “User Anonymizer for Jira” to display our add-on “User Anonymizer for Jira (GDPR)”. Click the Buy Now or Free Trial button to install the app.

If the installation was successful, a new section “User Anonymizer” appears in the administration. This is where the anonymization of users takes place. If this section is not visible, please ensure that all required modules of the add-on are enabled. For this, you should select the “User Anonymizer for Jira (GDPR)” from the list of installed apps.

Licensing

The app needs a valid license to have all the provided features working. Valid licenses include full licenses, renewal licenses, or 30-day trials and are available on the Atlassian Marketplace. The license model is the same as the one Atlassian uses for its products – for further information, see Atlassian’s documentation on app licensing.

To get a license and provide it for the plugin, please carry out the following:

• Go to the license settings page (Administration > Apps > “Manage Apps”: Extend “User Anonymizer for Jira (GDPR)”)

• Use the links to create a new license at the Atlassian Marketplace (use “Free Try” to get a new trial license or “Buy Now” to purchase a full license), or copy a license you got from Actonic.

• Enter the license key in the license screen.

Without a valid license, the User Anonymizer shows the message “Invalid or missing license key” instead of the User Anonymizer configuration screen.

Prepare your Jira system

To use “User Anonymizer for Jira (GDPR)” you should first create a technical anonymous Jira user. Go to Jira User management and create a user, for example with the username “anonymous”. Once created, please edit the user properties and set the user inactive.

You may choose the name freely, but it should clearly be identified as an anonymous technical user. It is also possible to create more than one anonymous user with different names.

But remember, every anonymous user should be set inactive to avoid logins. Anonymous users may have advanced permissions (for example, if set as project lead by the anonymization process).