# Sonar.issue.ignore.multicriteria doesn't work on common-c:InsufficientCommentDensity

**URL:** <https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049>\
**Category:** SonarQube Server / Community Build\
**Tags:** scanner\
**Created:** [March 23, 2019, 7:52am UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049 "2019-03-23T07:52:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![bgoglin](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@bgoglin](https://community.sonarsource.com/u/bgoglin)\
**Post date:** [March 23, 2019, 7:52am UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/1 "2019-03-23T07:52:32Z")

</div>

Hello  
I am using sonar scanner 3.2.0.1227 on Ubuntu 18.04. I use sonar.issue.ignore.multicriteria for ignoring several rules from rats and cppcheck, no problem. But I can’t get that to work on “common-c” rules. Tried for both InsufficientLineCoverage and InsufficientCommentDensity, doesn’t seem to do anything. Tried with prefix “common-c:” or “c:” or nothing.  
Thanks  
Brice

---

<div class="post-metadata">

**Author:** ![julienlancelot](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/julienlancelot/32/68225_2.png) [@julienlancelot](https://community.sonarsource.com/u/julienlancelot)\
**Post date:** [September 18, 2020, 3:10pm UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/2 "2020-09-18T15:10:40Z")

</div>

Hi @bgoglin,

Sorry for the delay in replying to you.

In fact, as descrbide in the [related documentation,](https://docs.sonarqube.org/latest/project-administration/narrowing-the-focus/) exclusion parameters should be set in at UI (or web service) level, and not at scanner level.

Regards,  
Julien Lancelot

---

<div class="post-metadata">

**Author:** ![bgoglin](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@bgoglin](https://community.sonarsource.com/u/bgoglin)\
**Post date:** [September 18, 2020, 5:05pm UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/4 "2020-09-18T17:05:42Z")

</div>

Hello  
Thank you, I’ll try that.  
It’d be nice to clarify why exclusion works for some rules and not for others.  
Brice

---

<div class="post-metadata">

**Author:** ![bgoglin](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@bgoglin](https://community.sonarsource.com/u/bgoglin)\
**Post date:** [September 19, 2020, 6:40pm UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/5 "2020-09-19T18:40:43Z")

</div>

Indeed @julienlancelot it works. But when you want to ignore 25 rules, duplicating a text configuration file is muuuuuuuch easier than duplicating 25 lignes in every project/branch in a web interface. Is there a way to factorize these rules somewhere to avoid the annoying duplication whenever I add a new project/branch or a new rule?  
Thanks

---

<div class="post-metadata">

**Author:** ![julienlancelot](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/julienlancelot/32/68225_2.png) [@julienlancelot](https://community.sonarsource.com/u/julienlancelot)\
**Post date:** [September 21, 2020, 7:33am UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/6 "2020-09-21T07:33:47Z")

</div>

Hi @bgoglin,

First of all, first for confirming that you were able to make it work using server settings.

Now, about the way to configure many project/branch =\> For branches, no need to do anything as long as it’s done at project level !  
You can also use web service [api/settings/set](https://next.sonarqube.com/sonarqube/web_api/api/settings/set) to automate this on many projects.

I’ve a question for you : why do you need to ignore so many rules ? Why don’t you ignore them in your quality profile ?

---

<div class="post-metadata">

**Author:** ![bgoglin](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@bgoglin](https://community.sonarsource.com/u/bgoglin)\
**Post date:** [September 22, 2020, 7:46am UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/7 "2020-09-22T07:46:42Z")

</div>

Thanks @julienlancelot, I asked my admin to create a quality profile, that’s indeed a good way to factorize all this, and seems to work fine. Most of the rules we are ignoring are dumb reports from cppcheck such as “you need 25% more comments in your code”, or “this FIXME should be handled”, and many other things that are obvious.

---

<div class="post-metadata">

**Author:** ![julienlancelot](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/julienlancelot/32/68225_2.png) [@julienlancelot](https://community.sonarsource.com/u/julienlancelot)\
**Post date:** [September 22, 2020, 8:46am UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/8 "2020-09-22T08:46:21Z")

</div>

I’m happy to read that using Quality Profiles is solving your issue !

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/system/32/31083_2.png) [@system](https://community.sonarsource.com/u/system)\
**Post date:** [September 29, 2020, 8:46am UTC](https://community.sonarsource.com/t/sonar-issue-ignore-multicriteria-doesnt-work-on-common-c-insufficientcommentdensity/8049/9 "2020-09-29T08:46:23Z")

</div>

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