The report per developer is meant to get an overview of who is creating Sonar issues, code duplications, failing unit tests etc., but also who is fixing the issues.
It could then be used to create a sort of competition among the developers to write better code. (The one who creates the most issues in a month has to bring cake for the team )
For this SonarQube would need run the analysis to store it’s results for every commit made by a developer. The delta is then the number of issues created/fixed by this developer.
To make this report complete a couple of things may need to be added:
- Running SonarQube on older revisions so to complete the historical data if not present yet
- Also complete Sonar analysis for failing builds (unit test analysis may not be possible, but code analysis should work). A failing build could be marked in a specific category of issues and thus also linked to the respective developer.