[
http://jira.codehaus.org/browse/MCHANGES-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Parkinson updated MCHANGES-245:
------------------------------------
Attachment: MCHANGES-245-maven-changes-plugin.patch
I have created a possible solution to the ticket based on adding a new
configuration parameter "issueTypes". The parameter is a map that takes the
action type as the key and the value as a comma separated string of issue types
e.g.
<issueTypes>
<add>New Feature, Story, Epic</add>
</issueTypes>
If action type is not defined in the map (The example doesn't defined "fix" or
"update") the default issue types are used for the undefined action types.
> Custom mapping of IMS issue types to action types for announcements
> -------------------------------------------------------------------
>
> Key: MCHANGES-245
> URL: http://jira.codehaus.org/browse/MCHANGES-245
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: announcement
> Affects Versions: 2.4
> Reporter: Alan Parkinson
> Attachments: MCHANGES-245-maven-changes-plugin.patch
>
>
> The current version only maps "Bug", "New Feature" and "Improvement" issues
> types to "fix", "add" and "update" actions. If the issue type from the IMS
> isn't recognized the default action type is blank and this leads to the issue
> not being included within the announcement when using the default template.
> This set of supported issue types can be limiting with a modern JIRA
> installation as is it has a greater range of issue types and can be extended
> with additional types. The most flexible solution for JIRA and other IMSes
> would be to allow the the mapping of issue types to action types.
--
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
