Hi,
We need the ability to configure the long-lived branch regexes in SonarQube Cloud at the time a new project is created, even when the project is still empty and no analysis has been performed yet.
It appears that this is no longer possible, or at least we are unable to find where to do it. This change is creating operational issues for us.
In many cases, project creation and project onboarding happen at different times. The project may be created in SonarQube Cloud days or even weeks before the first analysis is executed. As SonarQube Cloud administrators, we are often not aware of when that first analysis will occur.
As a result, we frequently find ourselves having to adjust the long-lived branch configuration after analyses have already been submitted to SonarQube Cloud. Since branch type classification is determined when a branch is first analyzed and cannot be changed afterward, this can lead to branches being incorrectly classified, with no way to correct them later.
Would it be possible to restore the ability to configure the long-lived branch pattern at the project level before any analysis exists?
We do have the option to define a pattern at the organization level, but different portfolios and projects may have specific branching strategies and naming conventions. For this reason, having the ability to configure the pattern directly at project creation time would be extremely valuable and would help avoid misclassification issues during onboarding.
Thank you for your consideration.
Regards
Bruna