The "Anonymized Project View" application helps you anonymize user communication when customers and contractors work in the same Jira projects. The application anonymizes names of other company users in all project views on the fly, without database changes.
The application features are as follows:
Project board view for an Administrator or "True-Sight" User (no users are shown anonymized):
Project board view for a Customer's User (contractor's users are shown anonymized):
Project board view for a Contractor's User (customer's users are shown anonymized):
Issue view for a Customer's User:
Issue view for a Contractor's User:
Issue view for a Contractor's User, where:
History view for a Customer's User:
History view for a Contractor's User:
Before configuring project anonymization, you must configure Jira users and user groups.
It is assumed that the customer and contractor companies work in the same Jira projects.
Create one company user for each company that works in the anonymized Jira projects. Company users are shown instead of the original users at project views for users of other companies. For company name anonymization, use made-up names.
To access this page, click Jira Administration -> User Management.
The user appears in the user list.
TIP: You can have one or more company users for a company. For example, use several users when you need to distinguish contractor company offices, such ContractorLondon or ContractorParis.
For anonymization, create a group and add all company users to this group.
To access this page, click Jira Administration -> User Management > Groups.
The group appears in the group list.
The users appear in the "Group member(s)" box.
Regardless of the configuration, the anonymization does not affect system administrators. Their names are anonymized as the other names, but system administrators see original names of all users.
In addition to system administrators, you can configure a "True-Sight" group whose members must not be affected by anonymization (for example, top managers). At the same time, their names will be anonymized as the other user names.
Create a "True-Sight" group and add users to this group, as appropriate.
Grant permissions for modifying all anonymized projects to the anonymization group. We recommend to add the anonymization company group to the Administrators project role.
Note: Granting Administrator permissions to the anonymization group does not raise security issues because no real users work from the company users.
To access this page, click Project Settings -> Users and roles.
We assume that you already have the Anonymized Project View application installed. Otherwise, install the plugin from https://marketplace.atlassian.com/apps/1219392/anonymized-project-view?hosting=server&tab=overview
In addition, you need to patch Jira as follows:
WARNING: Users that are included in the anonymization configuration will be anonymized in the entire Jira, not only in the specific Jira projects. Therefore, carefully configure users and anonymization settings for the anonymization to apply to the appropriate users only.
To access this page, click Jira Administration -> Add-ons -> ANONYMIZED PROJECT VIEW -> Anonymization Configuration.
Users of this group, regardless of their companies, will see original non-anonymized names for all users in Jira. At the same time, their names will be anonymized as the other user names.
The anonymization starts immediately after you save the configuration.
For anonymizing Jira project users, assign all the users to the appropriate company users (defined in Creating Users for Companies).
WARNING: Non-assigned users will be neither anonymized, nor affected by the anonymization.
To access this page, click Jira Administration -> Add-ons -> ANONYMIZED PROJECT VIEW -> User Configuration.
These users will now be anonymized using their company names.
When several customer or contractor parties work in Jira, you can define clusters of sibling companies to be mutually de-anonymized. At the same time, these companies will be commonly anonymized for other companies or clusters.
To access this page, click Jira Administration -> Add-ons -> ANONYMIZED PROJECT VIEW -> De-Anonymization Parties Configuration.
The "Add joint company configuration" display opens.
The cluster configuration appears on the "De-Anonymization Parties Configuration" display.
The "Anonymized Project View" application's health check determines users that are not assigned to any of the companies in the User Configuration (see Assigning Users to Companies). Such users will be neither anonymized, nor affected by the anonymization, therefore it is recommended to assign these users to the appropriate companies.
To run a health check for projects:
To access this page, click Jira Administration -> Add-ons -> ANONYMIZED PROJECT VIEW -> Anonymization Configuration.
Alternatively, if the health-check warning does not appear, navigate to the "Troubleshooting and support tools" page in Jira.
To access this page, click Jira Administration -> System -> Troubleshooting and support tools.
The "User Configuration (Missing Companies)" page opens.
(Optionally, assign users to companies from the User Configuration page as described in Assigning Users to Companies)
These users will now be anonymized using their company names.