[
http://jira.codehaus.org/browse/MCHANGES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200526#action_200526
]
Mark Derricutt commented on MCHANGES-141:
-----------------------------------------
Rereading through the patch I still think it works fine, however - the variable
name I used for {{fixIssue}} is badly named. As thats assigned inside a loop
of the {{issue.getFixVersions()}} iterator, it contains the Sting value of a
release, such as "1.2.7", _if_ the {{releaseMap}} doesn't contain this string
as a key, a new {{Release}} instance is created and put in the map.
So the map isn't keyed by the issue, but the fixFor for the issue. Renaming it
so say {{fixVersion}} makes it more clear. It'd be great to have this in the
plugin.
> Jira Report fails to pick up issues that contain multiple fix-for elements.
> ---------------------------------------------------------------------------
>
> Key: MCHANGES-141
> URL: http://jira.codehaus.org/browse/MCHANGES-141
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.1
> Reporter: Mark Derricutt
> Attachments: multipleFixFors.patch
>
>
> When a jira ticket is associated with multiple versions in its fix-for list,
> the report fails to correctly report the issues.
> A patch is attached which collects each fix for into a List of strings, and
> updates the report to include them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
