Branch Visibility Issue After Upgrade to SonarQube Community 26.1.0 in Dev

[Thilagam_Subburaj]

Must-share information (formatted with Markdown):

• which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)- Sonarqube Community build
• how is SonarQube deployed: zip, Docker, Helm - Docker
• what are you trying to achieve
• what have you tried so far to achieve this

We are planning to upgrade our SonarQube Community Edition from v25.1.0.102122 to v26.1.0.118079.
As part of validation, we upgraded our Dev instance to v26.1.0.118079 and observed a change in branch visibility.

Observed Behavior

• In the SonarQube UI, only the main branch is visible for projects.

• develop, feature, and release branches are not visible in the UI.

• However, under Administration → Background Tasks, we can see analysis tasks being executed successfully for feature and release branches.

• This indicates that branch analyses are still processed by the server, but they are not displayed in the UI.

(Screenshots attached for reference.)

Previous Behavior

• In v25.1.0.102122 (Community Edition), we were able to see develop and feature branches in the UI in the same Dev environment.

• No changes were made to CI configuration or project keys as part of the upgrade.

Questions

1. Is the absence of non‑main branches in the UI an expected behavior change in SonarQube Community Edition v26.1.0?

2. If yes, could you please confirm and point us to the relevant documentation or release notes?

3. If not expected, are there any configuration changes or migration steps required to restore branch visibility?

[Thilagam_Subburaj]

@Colin Could you let us know if this is expected behavior in the Community edition? If so, please confirm and share the relevant documentation or release notes.

[ganncamp (G Ann Campbell)]

Hi,

I invite you to familiarize yourself with the FAQ. First:

What is @name mentioning? Should I do it?

@name mentioning is when you type someone’s username with an @ preceding it. Doing this sends a notification to the user. Depending on their settings, it may also send them an email message.

In general, it is considered bad form to @name mention someone not already engaged in the conversation. Please don’t do it.

Second:

I created a topic, when can I expect a response?

This is an open community with people volunteering their free time to provide assistance. We’re eager to contribute to the community, but you are not guaranteed a fast response.

Be patient

• Wait a few days before bumping a topic that hasn’t received a response.
• Do not @name mention individuals not involved in the topic.

And finally, Community Build does not support branches and never has. So your experience is entirely expected.

 
HTH,
Ann

[Thilagam_Subburaj]

Hi Ann Campbell,

Apologies for mentioning the name, can I get any reference document, so that I can share it with users and management.

[ganncamp (G Ann Campbell)]

Hi,

I’m not sure what to tell you here. We don’t typically document what’s not in a product. There’s the pricing page, that’s clear that branch analysis is available in Developer Edition. And perhaps the Community Build docs which lack a single mention of branch analysis?

 
Ann