[
http://jira.codehaus.org/browse/MCHANGES-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229726#action_229726
]
Dennis Lundberg commented on MCHANGES-204:
------------------------------------------
Yes, developers and testers are aware of and works with SNAPSHOTs, but project
owners and end users may (should) not know about them. So putting SNAPSHOT
versions in JIRA is wrong in my opinion.
Yes, JIRA users make mistakes and forget to set fix versions and other required
field. This is where JIRA workflows comes in handy. They can prevent this from
happening. However I don't think it's the job of this reporting plugin to help
your developers use JIRA the way you want them to.
> Invalid JIRA issues are selected to report
> ------------------------------------------
>
> Key: MCHANGES-204
> URL: http://jira.codehaus.org/browse/MCHANGES-204
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira-report
> Affects Versions: 2.3
> Reporter: Krashan Brahmanjara
>
> If Jira contains tasks for version not specified or version with '-SNAPSHOT'
> suffix that are no reported items.
> Current code cut -SNAPSHOT from current version so nothing is selected.
> Patch for JiraReportGenerator
> line 409
> {noformat}
> - //if ( issue.getFixVersion() != null && issue.getFixVersion().equals(
> releaseVersion ) )
> + if ( issue.getFixVersion() == null || issue.getFixVersion().equals(
> releaseVersion ) || issue.getFixVersion().equals( currentVersion ))
> {noformat}
--
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
