[
http://jira.codehaus.org/browse/MCHANGES-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225414#action_225414
]
Michael Wenig commented on MCHANGES-202:
----------------------------------------
There is a difference between the type of a change and the type of an issue.
The existing type attribute is limited to 'add', 'update', 'fix' and 'remove'
and expresses the kind of change at the source level.
When you compare the sample changes report with the sample jira report (
http://maven.apache.org/plugins/maven-changes-plugin/changes-report.html vs.
http://maven.apache.org/plugins/maven-changes-plugin/jira-report.html)
you can see that on the jira report for every change the type of issue is
mentioned (Bug, New Feature, ...). The changes-report is only showing an image
about the type and the possible types are predefined. SO there is no
possibility to mention the type of the issue (like a UserStory) except entering
it in the description.
If you try to achieve a report like the jira-report using the changes.xml there
is a missing issueType which is entered as text in the report (and perhaps the
report is grouped by the issueType):
Something like
|[type-image]|UserStory|TEST-123|bla bla bla||micha||
> Enhance action-tag with a type attribute
> ----------------------------------------
>
> Key: MCHANGES-202
> URL: http://jira.codehaus.org/browse/MCHANGES-202
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: changes-report
> Affects Versions: 2.3
> Reporter: Michael Wenig
>
> When using the manual created report there is only the possibility to set an
> issue id.
> it would be nice if there were also an attribute issueType (e.g. UserStory,
> Bug, ...)
--
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
