Issue Assignment

[Chacha (Chadev)]

SonarQube Community 25.3

I have configured ldap with sonarqube community.
So to sign in to sonar I can use my company username and password.

When I scan code that its scm is git, sonar automatically maps the issue to a user based on the author of the issue.

However when scm is SVN, sonar is not mapping issues to corresponding users.

One thing I noticed is that when scm is git, the author of the issue is the email of the author
ex: john.doe@domain.com

But for svn the author is just the username:
ex: john.doe

Maybe this is the problem, please advise how to solve it
Also note that both git and sonar are configured based on the same active directory

[Colin]

Hey there.

@Chacha

But for svn the author is just the username:
ex: john.doe

Is this the same username that your user has in SonarQube?

[Chacha (Chadev)]

I am not sure

From admin I went to administration > security > users, this is how users are appearing:

Admin user:
Administrator (in bold)
admin (under administrator)

Other users:
John Doe (in bold)
john-doe1234 (under John Doe)
john.doe@domain.com (under john-doe1234)
LDAP_default: john.doe (under john.doe@domain.com)

[Colin]

Thanks.

@Chacha

john-doe1234 (under John Doe)

This is the username. Since it’s not john.doe exactly, the issue won’t be mapped. Username and e-mail addresses are considered possible SCM accounts by default.

However, you can add john.doe as an SCM account by updating the details of the user.