How to update/refresh existing issues with new sonarqube users?

1,657 views
Skip to first unread message

gilles...@gmail.com

unread,
Jun 30, 2016, 5:30:16 AM6/30/16
to SonarQube
Hi,
We use LDAP authentication for SQ 5.6.
I first ran analysis with sonar, it could assign issues to users who have already logged into SQ.
When i ran a second time, it did not update the issues with the new comers (who have logged in between run 1 and 2)
Is there a way to make SQ update automatically the existing issues?
Thank you, g->




Julien Lancelot

unread,
Jul 1, 2016, 8:41:04 AM7/1/16
to SonarQube, gilles...@gmail.com
Hi Gilles,

If yes, this means that issues have been assigned to the default assignee during first analysis and they won't be assigned to anyone else after.
If no, could you please search for issues with the api/issues/search WS of the project and look after 'author' and 'assignee' properties ?

Thanks,
Regards,
Julien Lancelot

gilles...@gmail.com

unread,
Jul 4, 2016, 7:43:17 AM7/4/16
to SonarQube, gilles...@gmail.com
Hello Julien,
There is no default assignee. For the second part "Web_API", how should i start with this?
Are existing issues supposed to be updated if assignee is matched afterwards?
Thank you
Best Regards, gilles

Julien Lancelot

unread,
Jul 7, 2016, 3:14:14 AM7/7/16
to gilles...@gmail.com, SonarQube
Hi Gilles,

In fact I was wrong, we never update the issue assignee after it was created, because we dont do the difference between : 
  • Issue has never been assigned
  • Issue was assigned to someone but then the assignee was removed
So the behavior you're encountering is the expected behavior.

Regards,

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/0726b803-beaa-400a-a582-1c74a7a79cb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Julien LANCELOT | SonarSource

pmar...@gmail.com

unread,
Feb 8, 2017, 12:01:57 PM2/8/17
to SonarQube, gilles...@gmail.com
Hi Julien,

Is there a fix for this in the meantime?
I set up SonarQube for my company but the users are not created until they log in for the first time (LDAP).
Obviously I already ran an analysis. I don't want to wait for everyone to log in, then remove the project and re-create it.

Is this on your bug list? Can I vote on it or something?

Peter

Op donderdag 7 juli 2016 09:14:14 UTC+2 schreef Julien Lancelot:

Julien Lancelot

unread,
Feb 9, 2017, 3:01:37 AM2/9/17
to pmar...@gmail.com, SonarQube, gilles...@gmail.com
Hi Peter,

If you want to assign issues to a user, you can use the bulk update of issues by filtering issues by author.
Otherwise, in 6.3 you'll be able to provision non-local users in SonarQube so that the user exist before he authenticates : https://jira.sonarsource.com/browse/SONAR-8715

I hope it will help.
Regards,



For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages