New indicators lose the branch name

SonarQube Server / Community Build
1

Hello,

In SonarQube 10.4.1 (build 88267), clicking on the Security, Reliability, and Maintainability links lose the selected branch information.

When you are in the default branch:

  • Project URL = https://SONAR_URL/dashboard?id=PROJECT_ID
  • Security link = https://SONAR_URL/project/issues?issueStatuses=OPEN%2CCONFIRMED&impactSoftwareQualities=SECURITY&id=PROJECT_ID
  • Reliability link = https://SONAR_URL/project/issues?issueStatuses=OPEN%2CCONFIRMED&impactSoftwareQualities=RELIABILITY&id=PROJECT_ID
  • Maintainability link = https://SONAR_URL/project/issues?issueStatuses=OPEN%2CCONFIRMED&impactSoftwareQualities=MAINTAINABILITY&id=PROJECT_ID

When you are not in the default branch:

  • Project URL = https://SONAR_URL/dashboard?branch=BRANCH_NAME&id=PROJECT_ID
  • Security link = https://SONAR_URL/project/issues?issueStatuses=OPEN%2CCONFIRMED&impactSoftwareQualities=SECURITY&id=PROJECT_ID
  • Reliability link = https://SONAR_URL/project/issues?issueStatuses=OPEN%2CCONFIRMED&impactSoftwareQualities=RELIABILITY&id=PROJECT_ID
  • Maintainability link = https://SONAR_URL/project/issues?issueStatuses=OPEN%2CCONFIRMED&impactSoftwareQualities=MAINTAINABILITY&id=PROJECT_ID

The thing is that when you have the list of issues in the main branch and that you select another branch in the branch selector, you go back to the project home page.

Thus, to have the list of Security issues in a given branch, you would have to:

  1. Select the branch
  2. Click on “issues”
  3. Filter on the metric you want to display

Is this behaviour already known ?

Thanks,

BR

2

Hi,

To be clear, you

  • start from the project homepage, main
  • navigate to the issues tab and filter it
  • select a different branch from the dropdown (presumably because you want to compare the filter results to main)
  • land back at the branch homepage

?

TBH, I don’t think it’s a use case we considered. I’m going to flag this for the team.

 
Ann

4

Hello @ganncamp !

No, I start from the project homepage, then select a branch, then click on “Overall code” and click on a metric.

See you :wink:

5

Hi,

I’m not reproducing that in our dogfooding instance

Are you using a web context (i.e. additional path segment)?

 
Thx,
Ann

6

Hey,

Maybe this is indeed fixed in 10.5 ? I’ll try to do a screencast on Monday, would this suit you ?

BR

7

Hi,

We’re not available for synchronus stuff. We have fixed a couple problems already related to web context, which is why I asked if you’re using one.

 
Ann

8

Hey,

I was not talking about synchronous stuff, merely a gif screencast :wink:

9

There you go !

2024-03-25_11-11-26_firefox

10

Hi,

Thanks for the gif.

Are you using a web context?

 
Ann

11

Hello Ann !

What do you mean, “web context” ?

12

Hi,

By default, SonarQube is served at http://localhost:9000, but you can change the port by setting sonar.web.port in the sonar.properties file, and you can add a path (e.g. http://localhost:9000/sonarqube) by setting sonar.web.context.

 
Ann

13

Hello,

We are using the helm-chart to deploy SonarQube to an Azure Kubernetes cluster.

So we are using our internal URL, on port 443.

BR

14

Hi,

Thanks. I’ve flagged this for the team.

 
Ann

1 Like
16

Hello Mikaël,

Thank you for bringing this to us,
This bug will be fixed in 10.5: https://sonarsource.atlassian.net/browse/SONAR-21600

Thanks,

2 Likes
20

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.