SonarQube Version - SonarQube Data Center Edition v2025.1.1 LTA deployed through Zip
When I’m currently in a new (empty) project and try to switch to a different one using the top search bar, entering the project key and clicking on the first suggested result seems to reload the current project instead of navigating to the selected one.
Here’s what I tried:
I opened an empty project and used the top search bar to look for another project. I navigated through the suggestions using the arrow keys and selected a project by pressing the Enter key. However, instead of loading the selected project, it simply reloads the currently opened project.
And more importantly, when I run a search, arrow to a result and hit Enter on SonarQube, I’m not seeing URLs that end like that in my Network tab.
I’m particularly struck by those “middleware_service” URLs. Is that part of the project key in question?
When you try those URLs manually, are they still 404?
Can you access the project you were trying to reach via a click-thru from the Projects page? I’m wondering if this is because you don’t have perms to the project in question. (In which case the root problem is that you saw it in the search results, not that it’s not loading.)
Are both the projects (the one that is currently open and the one you are trying to open through search) empty? I forgot to mention that, in my case, both are empty projects.
Yes, that is part of the projectKey.
I am the administrator of this instance. I am also part of the group which has complete access to these projects.
Also, the URL in the console/network tab looks like this,
It’s quite possible to be a global admin and not have Browse on a project. Can you access this project directly via, e.g. the Projects page?
Does this happen only with empty projects?
Also, how were these empty projects created? Your error message indicates that they weren’t created from an DevOps platform import, and if they’re empty that implies they weren’t created on first analysis…?
Yes, we have a separate group with all the permissions to all the projects on the server. This group is part of each of our permission templates and is applied right after the project creation.
Yes, this seems to happen only with empty projects.
We create them through APIs. Whenever teams request for a new project, we create them and share the projectKey, which they’ll configure for use in their pipelines.
I’m not sure you’ve answered this question for me:
At this point, I’m guessing something crucial to the UI? to that search functionality? doesn’t get initialized in your API initialization. I’d like to nail this down a little further before I call in the experts.
Hi,
Thanks for your feedback @aravindnss! I was able to reproduce this issue in the LTA version.
Unfortunately, this issue doesn’t fall under the categories of our support policy for patch releases (only vulnerability or blocker issues are addressed). This means we won’t be able to fix it for LTA.
Good news though: this is already fixed in the latest version of SonarQube Server.