[MCHANGES-385] JIRA Report for Changes plugin Invalid browse URL for issueManagement
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
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.
Description
John Fox opened MCHANGES-385 and commented
If the issueManagement URL is defined as a JQL query the changes plugin fails with
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
<issueManagement>
<system>JIRA</system>
<url>https://issues.apache.org/jira/issues/?jql=component%20%3D%20changes.xml</url>
</issueManagement>
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:
1 votes, 5 watchers
- Dominant language
- Java
- Stars
- 15
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/maven-changes-plugin
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/maven-changes-plugin#650 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#633 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
apache/maven-changes-plugin#619 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/maven-changes-plugin#610 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
apache/maven-changes-plugin#608 ·
All issues in apache/maven-changes-plugin
Similar issues
-
area/plugin
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kestra-io/plugin-kestra#190 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
integra-team-red/meet-map#249 ·
-
[Studio][Bug] Cancelled create-user dialog keeps the password and admin switch for the next attempt Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/rocketmq-dashboard#5064 ·