[MCHANGES-385] JIRA Report for Changes plugin Invalid browse URL for issueManagement

**[John Fox](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=john%20fox)** opened **[MCHANGES-385](https://issues.apache.org/jira/browse/MCHANGES-385?redirect=false)** and commented

If the issueManagement URL is defined as a JQL query the changes plugin fails with

```java
10:24:52 [INFO] Generating "JIRA Report" report --- maven-changes-plugin:2.12.1:jira-report
10:24:52 [WARNING]
10:24:52 java.lang.IllegalArgumentException: Invalid browse URL
10:24:52 at org.apache.maven.plugin.jira.JiraHelper.getJiraUrlAndProjectName (JiraHelper.java:229)
10:24:52 at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute (RestJiraDownloader.java:115)
10:24:52 at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute (AdaptiveJiraDownloader.java:45)
10:24:52 at org.apache.maven.plugin.jira.JiraMojo.executeReport (JiraMojo.java:346)
```

Example IssueManagement

```xml

JIRA
https://issues.apache.org/jira/issues/?jql=component%20%3D%20changes.xml

```

In our projects a maven artifact correlates to a JIRA component so for an individual issueManagement site URL we want to be able to see all of the issues tied to that component. This is only an issue if the jira report is used for the changes report this works without issue.

---

**Affects:** 2.12.1

**Remote Links:**
- [GitHub Pull Request #8
](https://github.com/apache/maven-changes-plugin/pull/8)

1 votes, 5 watchers

Start with the JIRA report path in JiraHelper.java, then read RestJiraDownloader.java and the stack trace to see how the issueManagement URL is parsed. Use the JQL URL from the issue as a reproduction case; done means the JIRA report accepts it and lists issues for the requested component without raising Invalid browse URL.

Written by the indexing model from the issue text.