{"id":234,"date":"2026-10-13T00:30:52","date_gmt":"2026-10-13T00:30:52","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/04\/14\/issuemanagement-in-maven\/"},"modified":"2026-10-13T00:30:52","modified_gmt":"2026-10-13T00:30:52","slug":"issuemanagement-in-maven","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/issuemanagement-in-maven\/","title":{"rendered":"Maven issueManagement: Configure Issue Tracker Metadata Correctly in pom.xml"},"content":{"rendered":"\n

Originally published on 2010-04-14; fully revised and updated.<\/em><\/p>\n\n\n\n

Maven\u2019s issueManagement<\/code> section publishes where bugs and feature requests for a project should be tracked. For maintainers and consumers, this keeps tracker details in project metadata instead of scattered across docs or team chat.<\/p>\n\n\n\n

\"issueManagement<\/a><\/figure>\n\n\n\n

What issueManagement is for<\/h2>\n\n\n\n

The issueManagement<\/code> block is part of Maven project metadata in pom.xml<\/code>. It tells users and tools which issue tracker to use and where to access it.<\/p>\n\n\n\n

issueManagement elements<\/h2>\n\n\n\n

The original post listed two core elements. Those remain the practical fields teams set.<\/p>\n\n\n\n

Element<\/th>Description<\/th>Example value<\/th><\/tr><\/thead>
system<\/td>Name of the issue tracker used by the project.<\/td>Jira<\/td><\/tr>
url<\/td>Direct URL to the project\u2019s issue tracker.<\/td>https:\/\/jira.example.com\/projects\/APP<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

POM configuration examples<\/h2>\n\n\n\n

Minimal snippet<\/h3>\n\n\n
<issueManagement<\/span>><\/span>\n  <system<\/span>><\/span>GitHub Issues<\/system<\/span>><\/span>\n  <url<\/span>><\/span>https:\/\/github.com\/example-org\/example-repo\/issues<\/url<\/span>><\/span>\n<\/issueManagement<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Inside a project POM<\/h3>\n\n\n
<project<\/span>><\/span>\n  <modelVersion<\/span>><\/span>4.0.0<\/modelVersion<\/span>><\/span>\n  <groupId<\/span>><\/span>com.example<\/groupId<\/span>><\/span>\n  <artifactId<\/span>><\/span>demo-app<\/artifactId<\/span>><\/span>\n  <version<\/span>><\/span>1.0.0<\/version<\/span>><\/span>\n\n  <issueManagement<\/span>><\/span>\n    <system<\/span>><\/span>Jira<\/system<\/span>><\/span>\n    <url<\/span>><\/span>https:\/\/jira.example.com\/projects\/DEMO<\/url<\/span>><\/span>\n  <\/issueManagement<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
How metadata flows to users and tooling<\/h2>\n\n\n\n
\nflowchart LR\n    A[Edit pom metadata] --> B[Commit and build]\n    B --> C[Generate effective pom]\n    C --> D[Publish artifact or site]\n    D --> E[Users discover tracker link]\n    E --> F[Issues and requests go to correct system]\n<\/pre>\n\n\n\n
This workflow is simple but high impact: clean metadata reduces misrouted bug reports and improves project discoverability.<\/p>\n\n\n\n
Common system values and URL patterns<\/h2>\n\n\n\n
system value<\/th>Typical URL pattern<\/th>When teams use it<\/th><\/tr><\/thead>
Jira<\/td>https:\/\/jira.example.com\/projects\/KEY<\/td>Enterprise project tracking<\/td><\/tr>
Bugzilla<\/td>https:\/\/bugzilla.example.com\/<\/td>Legacy or established bug workflows<\/td><\/tr>
GitHub Issues<\/td>https:\/\/github.com\/org\/repo\/issues<\/td>GitHub-hosted repositories<\/td><\/tr>
GitLab Issues<\/td>https:\/\/gitlab.com\/group\/project\/-\/issues<\/td>GitLab-hosted repositories<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Validate what Maven resolves<\/h2>\n\n\n\n
Use the effective POM to verify the final metadata seen by Maven (especially if parent POMs are involved).<\/p>\n\n\n
mvn -q help:effective-pom | sed -n '\/<issueManagement<\/span>><\/span>\/,\/<\\<\/span>\/issueManagement<\/span>><\/span>\/p'<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Original references<\/h2>\n\n\n\n