which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
how is SonarQube deployed: zip, Docker, Helm
what are you trying to achieve
what have you tried so far to achieve this
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
Version 9.9.1
During the build process, the build succeeds. However, upon visiting the SonarQube website, I cannot access the scanned project despite having the necessary permissions configured. It seems the project is only visible after the Admin manually refreshes the page, toggling the option in Project → Background Task, even though I also have admin permissions. I’ve attached some screenshots. Please pardon my attempt at humor while doing so.
This pertains to a user’s project that, once created, isn’t visible to them on the main page. However, with admin permissions granted to the user, accessing the admin options reveals the project under Background tasks. Clicking on the project yields a page loaded as depicted in the provided snippet above.
Furthermore, the default template has been configured, creator settings established, and user access and permissions granted for this test. Despite these preparations, upon attempting to run a new project, the outcome remains consistent: the project does not surface for the user. It’s only discoverable within the admin options, located under “Background tasks” within the “Projects” section.
It sounds like the user doesn’t have Browse access to the project. You can have Admin access to a project (or even an entire instance of SonarQube) but still lack browse permissions. I suggest verifying the permissions at the project level.
The project encounters an issue where, despite the main admin granting similar permissions to another user, both the new user and the project creator are unable to view the project. However, the main admin can adjust settings to make it visible to the secondary admin and the project creator. We’ve modified the default template and found that for the project creator to access their work, they need both the “sonar-user” and the creator’s browse options toggled. If only the “sonar-user” option is toggled without the creator’s browse option, access is still restricted unless both toggles are enabled for both the creator and the sonar user. I’ve only just discovered this today, so I’m unsure if it completely resolves the issue.
