Facing issue in language rules in feature branch

We are using SonarQube 10.4.1 in our project.
Hi,
I am facing issue in language rules in feature branch under the issue section. Even languages were added explicitly added for the feature branch under Quality Profiles still JavaScript is not enabled for feature branch.

We can see the languages added in the Quality profiles but languages are not reflected under the issue section.


Thank you!

Hi @Colin same issue here, can you please help us to resolve the issue.

Thanks!

Hi @Colin , can you please help on this

Hey @balaji_g and @Kiruthiga1

Please do not tag users in threads they are not involved in. The FAQ is very clear on this.

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.

Contribute as much as you expect to receive

  • Contribute to the community (helping others) as much as you expect to receive help.

It is not a replacement for more structured support

  • If you need SLAs, guaranteed response, privacy, SonarSource also offers Commercial Support.

You may think this bumps a thread up to the top of my list, but it does the exact opposite.

Hi,

As Colin said, don’t @ users not already involved in a thread. It doesn’t move your thread up their priority list. Just the opposite.

That’s… not actually possible.

Analysis is multi-language by default*. A profile will be applied automatically for each language detected in the analysis. If you’re not seeing JavaScript in the list of languages on the issues page, then either no JS files were detected or … they were perfect. Since that’s not likely (no offence, we’re all human), the question is why they weren’t analyzed.

So, how are you analyzing? And with which scanner?

 
Ann

* Most of the time. It needs to be turned on for Java with sonar.gradle.scanAll / sonar.maven.scanAll. Previous versions of SonarScanner for .NET weren’t multi-language, but if you’re on the latest version, this is handled.