[
http://jira.codehaus.org/browse/MCHANGES-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252501#action_252501
]
Dennis Lundberg commented on MCHANGES-202:
------------------------------------------
So the problem is really that the action.type attribute is different from
issue.type (as used in JIRA).
I feel that best thing would be to change the set of values allowed in
action.type. It should be more like the issue type that is used in current
issue management systems. The problem is figuring out a reasonable set of
values. A standard JIRA installation has these values: Bug, New Feature, Task
and Improvement. My mapping of those values to the ones used in action.type
would look like this:
{noformat}
add <--> New Feature
update <--> Improvement
fix <--> Bug
remove <--> Task
{noformat}
That is something that we will have to face moving forward when this plugin
when we start to add more issue management systems.
Another question is whether to allow the user to add custom values for
action.type. The current XML schema allows it, but you don't get any icons for
those types, and because we currently don't print out the actual text for the
type - that would be a problem.
> 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.xml
> 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
