How to assign bugs and vulnerabilities in sonar cloud to an individual developer?

SonarQube Server / Community Build
1

Hello everyone, I’m implementing Sonar 25.9 Community code analysis in the repositories of the company I work for, I’m having difficulty associating Bugs/Code Smells with the developer who caused them, I wanted to know how I can do this in an automated way.

2

Hi,

Welcome to the community!

Issues should be assigned automatically to the last committer on the issue line. However, (there’s always a “but” :joy:) that committer must first have an account in SonarQube for that to work. Since you say you’re just getting going with SonarQube, I suspect that’s your hurdle.

 
HTH,
Ann

3

Hi, so the users already exist and have the same email address as Azure DevOps (I read somewhere that it would be necessary), but as soon as a bug is generated, it has a “Not Assigned” status. I thought it could be something in the pipeline, would that make sense?

4

Hi,

If you click in the left margin, next to an issue, you should see the ‘blame’ information assignment would be based on. Can you pick an issue and see if it matches the email/SCM info of an existing account in your organization?

 
Thx,
Ann

5

So, it should appear, but it says Not Assigned, like in the image. Is there anything else I can do to make this functionality work?

image
image1051×159 15.2 KB

6

Hi,

So you’ve identified an issue where the committer ID shown in the left margin is the same as the information for a developer account that existed in SonarQube before the analysis that created the issue ran?

Is the committer ID the same as the email? Listed explicitly as an SCM account? And is the spelling and casing identical?

 
Thx,
Ann