[
http://jira.codehaus.org/browse/MCHANGES-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-92.
-----------------------------------
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.0-beta-4
The new patch was really helpful and saved me some time, thanks!
I have applied the second patch with modifications. Most notably I moved the
default-value from JiraReportGenerator to JiraMojo. The reason is that
default-values for parameters in a mojo are automatically included in the
documentation.
A new 2.0-beta-4-SNAPSHOT has been deployed.
> JIRA Report Improvements
> ------------------------
>
> Key: MCHANGES-92
> URL: http://jira.codehaus.org/browse/MCHANGES-92
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira-report
> Affects Versions: 2.0-beta-3
> Reporter: Niall Pemberton
> Assignee: Dennis Lundberg
> Fix For: 2.0-beta-4
>
> Attachments: maven-changes-jira-report-improvements.patch,
> MCHANGES-92-jira-column-configuration.patch
>
>
> OK heres my wish-list to improve the JIRA report:
> - Be able to configure which columns are shown on the report
> - Make the following additional columns available on the report: Reporter,
> Type, Priority, Version, Fix Version and Component
> - Be able to configure the "Fix Version" to show on the report (rather than
> all versions)
> - Be able to configure which "types" are shown on the report (rather than
> all types)
> - Currently the configurable Status, Resolution and Priority values are
> ignored (because of bugs in the url parameters used)
> I realize the Fix Version and Types can be configured using the existing
> "filter" - but thats not a very user friendly feature.
> Attaching a patch which does all of the above.
--
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
