Facet(s) 'moduleUuids' require to also filter by project or organization

SonarQube Server / Community Build
,
1

Performed trial upgrade from SonarQube 5.6.7 to SonarQube 6.7.5 Community Edition on Windows Server 2016 using SQL Server 2016 and Java 8, and encounter a red dialogue box which appears at top of screen stating one of the following:

Facet(s) ‘moduleUuids’ require to also filter by project or organization
Facet(s) ‘directories’ require to also filter by project or organization
Facet(s) ‘fileUuids’ require to also filter by project or organization

When trying to use either the Module, Directory or File links from the Issues page, when the Code option has been used to navigate to a child / sub project.

Please review and advise if this is a bug, missing configuration or as intended.

2

Hi,

The Issues page is fetching data from Elasticsearch.
Try to delete Elasticsearch data and see if that helps.

Here are the steps:

  • stop your SonarQube server
  • delete the ElasticSearch index @ <sonar_install_dir>/data/es5
  • start your SonarQube server
  • wait for the startup to be complete (“Process[ce] is up” message recorded in the <sonar_install_dir>/logs/sonar.log ), which will take longer than usual since SonarQube will re-index all data

Greetings,
Kris

3

Hi Kris,

Performed steps suggested, but issue still present

Please advise

Regards
Carl

4

Hi Carl,

Can you share a screenshot of that "red dialogue box which appears at top of screen " ?

Kris

5

Hi Carl,

Could you please try to open the failing page in an private windows (is also called Incognito in Chrome) ?

Regards

6

Hi Julien

Issue still present when opening the failing page using Incognito mode in Chrome

Regards
Carl

7

Hi Kris

Please find requested screenshot

Regards
Carl

SonarQube-675-Facet-dialogue
SonarQube-675-Facet-dialogue.PNG1091×943 106 KB

11

Hi Carl,

Sorry for coming back lately on this, we’ve been able to reproduce this issue, I’ve created a JIRA ticket : https://jira.sonarsource.com/browse/SONAR-11261.

Please note that this issue will be fixed in 7.4, and no decision has been taken if we’ll fix it in 6.7.X.

Regards

12

Hi Julien,

Thanks for the feedback

Regards
Carl