I am new to SonarQube. We are analyzing 14 projects. When I first set this all up, I don’t believe SonarQube assigned old/existing issues to users on the first scan. Only new issues created after the first scan were assigned.
Now that we are getting ready to start using SonarQube for real, I deleted all the projects so we could start fresh. On the next scheduled scan (through Jenkins) it recreated all the projects. But it assigned all the issues to the developers. That’s 31,000+ old / existing issues that were assigned. We really only wanted new issues assigned as developers commit new code.
Could someone confirm whether or not those assignments of old/existing issues should have taken place on the first scan of the project?
If they shouldn’t have been assigned, any idea what I might have broken that caused it?
If they should have been assigned, what are my options for unassigning them? Bulk edit only allows 500 updates at a time. And if I do go through the process of unassigning them all, will they be re-assigned on the next scan?
I think I may have answered my own question but would appreciate if someone could confirm.
On the first scan of a project, all the old issues will be assigned to developers. I believe the possible reason I didn’t see this on our first scan is because I may not have had the SCM accounts, nor the default user configured yet. That may be why all the old issues were “un-assigned”.
Developers can filter on issues in new code. However, they have to first select a project. If they just click “Issues” → “My Issues” without selecting a project, there is no filter option for seeing issues on new code only. That filter option is only available if they first select a project and then select “Issues” → “My Issues”.
If an issue is updated to “unassigned”, it will stay unassigned during the next scan.
I can write a python script to use the web API to un-assign all old issues if we decide to go that route. We may do this to keep things simpler, cleaner and more focused on the new code as we onboard developers.