# Report Issues per Module for a Multi-Module Maven Project

**URL:** <https://community.sonarsource.com/t/report-issues-per-module-for-a-multi-module-maven-project/59601>\
**Category:** SonarQube Server / Community Build\
**Tags:** issues, maven, sonarqube\
**Created:** [March 9, 2022, 12:48pm UTC](https://community.sonarsource.com/t/report-issues-per-module-for-a-multi-module-maven-project/59601 "2022-03-09T12:48:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![harshi24](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@harshi24](https://community.sonarsource.com/u/harshi24)\
**Post date:** [March 9, 2022, 12:48pm UTC](https://community.sonarsource.com/t/report-issues-per-module-for-a-multi-module-maven-project/59601/1 "2022-03-09T12:48:55Z")

</div>

- The version of SonarQube: 9.2.4.50792
- A way to report issues per module for a multi-module maven project
- When a multi-module maven project is analyzed, the results do not have any filters to report the issues per each module. Is there a way to view the issues per module?

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 9, 2022, 5:41pm UTC](https://community.sonarsource.com/t/report-issues-per-module-for-a-multi-module-maven-project/59601/2 "2022-03-09T17:41:16Z")

</div>

Hey there.

Today, there is not. Hopefully someday [SONAR-12771](https://jira.sonarsource.com/browse/SONAR-12771) is implemented, which would allow you to filter to all issues in a directory (which usually maps neatly to modules). I’ve linked your thread to that ticket as as sign of support.

---

<div class="post-metadata">

**Author:** ![anon67236913](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@anon67236913](https://community.sonarsource.com/u/anon67236913)\
**Post date:** [March 9, 2022, 5:47pm UTC](https://community.sonarsource.com/t/report-issues-per-module-for-a-multi-module-maven-project/59601/3 "2022-03-09T17:47:05Z")

</div>

Hi,

had the requirement to have one Sonarqube project per submodule for specific reasons.  
Maybe this helps

> [@Mvn multimodule build, create single SQ projects](https://community.sonarsource.com/t/mvn-multimodule-build-create-single-sq-projects/11629):
>
> Hi, unfortunately we’re not running with Artifactory (yet), where Sonarqube integration seems much better according to [https://blog.sonarsource.com/fully-automated-promotion-pipelines-with-sonarqube-and-artifactory](https://blog.sonarsource.com/fully-automated-promotion-pipelines-with-sonarqube-and-artifactory) For deployments from Sonatype Nexus, i had to create a check whether an artifactversion is Sonarqube approved, means artifactversion = sonar.projectVersion and QualityGate = OK. With web api, e.g. [https://somesonarhost/api/project\_analyses/search?project=com.foo.bar:foobar&ps=500](https://somesonarhost/api/project_analyses/search?project=com.foo.bar:foobar&ps=500) …

Gilbert