Having aggregated and easily accessible nominative information can encourage a behavior that we'd rather avoid. The information can be used to measure the overall contribution of someone, and thus performance.
With this information, a Supervisor can go through the projects or even easier a portfolio and select the Author and Assignee information.
Person A: 300k LoC and only 20 Issues will get a Bonus because of this data. ...
Person B: 50K LoC and 30K issues will not get the bonus and for the next promotion he will be sorted out.
Also, because of labor regulations in several countries, some customers want to remove the ability to see aggregated personal information in SonarQube. For this purpose, they have to disable the SCM integration. The consequence is that they don't benefit from some important features.
We want to avoid this, but we don't simply want to stop collecting information regarding authors. They are useful for users to benefit from the auto-assignment of issues, and thus to see the issues they have to fix, receive notifications on new issues...
The Assignee facet can be used by some customers in the following cases:
- Find and reassign issues for someone leaving the company
- Find and reassign issues which are not assigned to anyone
We'll create a mode where aggregated personal information (Author, Assignee) will be removed from the UI, i.e. where the Authors and Assignee facets of the Issues page won't be available.
The Author of issues will still be collected. Auto-assignment and other features relying on personal information will continue to work.
Both Author and Assignee information can keep being accessible through the APIs (api/issues/search).
The parameter can be named: Disable aggregated nominative information, and will be turn off by default.