Auto issue assignment not working

[matad...@googlemail.com]

Hi

I'm trying the issue assignment on SonarQube 5.6 LTS and it doesn't seem to assign to a user correctly.  I expect this maybe an issue with our local set up so how can I get more logging information when analysis is run? I enabled maven -X for verbose logging but don't see any entries such as "assignment" "auto assign".

The user who is assigned an issue for a changed file from the nightly build hasn't actually ever appeared in the history for this file.

Many thanks

Matt

[G. Ann Campbell]

Hi Matt,

Is that user the default assignee for the project? (Administration > General > Default Assignee)

Ann

[matad...@googlemail.com]

thanks Ann, no that field is blank at both the project and global level

[Teryk Bellahsene]

Hello Matt,

Do you confirm that you don't see the assignee in the list of commits in SonarQube? YOUR_PROJECT > Code, then search for your file.

• What are the plugins and their versions installed on your instance?
• Is this problem recurrent? Is it always assigned to the same person?
• has the assignee several identities when you look at its profile?

Sincerely,

Teryk

[matad...@googlemail.com]

Thanks Teryk

1. The assignee doesn't appear in any of the commits in SonarQube
   
2. There are a large number of plug ins installed. Is there a way to export a list? I've attached screenshots showing all of them
3. The problem occurs for other users so isn't always the same person
4. No the assignee has only identity for the SCM account

As I mentioned originally is there no way we can enable verbose logging to understand how the assignment is being made internally within Sonar?

Thanks

[matad...@googlemail.com]

Perhaps there is an additional logging option I can enable within an internal sonar logger when issues assignment is performed?

[Teryk Bellahsene]

Hello,

Unfortunately, there's no logging at the assign phase (except if an scm account is not visible).
Please test the several actions:

• drop the directory data/es and restart the server
• check the SCM accounts assigned to the user that is automatically assigned
• then in your project page, go to Code then enter the file concerned. What is the SCM account on the line of the issues?
• update the Git plugin

Sincerely,

Teryk

[Teryk Bellahsene]

The data/es folder hold the Elastic Search data that is normally indexed and updated. Maybe there's some data mix up. I want to eliminate this possibility.

Teryk Bellahsene | SonarSource Software Developer http://sonarsource.com

On 11 October 2016 at 10:08, Matt Adamson <matad...@googlemail.com> wrote:

Thanks what does the data/es folder hold?

[matad...@googlemail.com]

thanks. I deleted the data/es folder and updated the git plug in from 1.1 to 1.2.  I'll let you know how subsequent analysis goes and if the correct user is now assigned

On Tuesday, 11 October 2016 09:11:13 UTC+1, Teryk Bellahsene wrote:

The data/es folder hold the Elastic Search data that is normally indexed and updated. Maybe there's some data mix up. I want to eliminate this possibility.

Teryk Bellahsene | SonarSource Software Developer http://sonarsource.com

On 11 October 2016 at 10:08, Matt Adamson <matad...@googlemail.com> wrote:

Thanks what does the data/es folder hold?

[Teryk Bellahsene]

Hello Matt,

How did it go? It the problem solved?

Sincerely,

Teryk Bellahsene | SonarSource Software Developer http://sonarsource.com

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/wJJj7EyA7Rs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/f99eda8e-b425-4f23-b7a1-ee756a174d28%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[matad...@googlemail.com]

Hi Teryk

The issue could well be related to 

https://groups.google.com/forum/#!topic/sonarqube/8HTQJGeZYyc%5B1-25%5D

which I created as a separate issue when SCM history did not look correct.

Let's close this issue for now

Many thanks

Matt

To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.