[
http://jira.codehaus.org/browse/MCHANGES-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145784#action_145784
]
Vincent Siveton commented on MCHANGES-124:
------------------------------------------
Since the filter is done in
JiraReportGenerator#getIssuesForCurrentRelease(List), I guess it will be easy
to ask JIRA to return all issues (ie without tempMax param) and apply the
filter/maxentries in Java. It will work only if currentVersion was set, in
other cases just apply the maxEntries as usual.
cons: could be time consuming if a project has a lot of issues (for instance
try given url on http://bugs.sakaiproject.org/jira/ )
> maxEntries is used in the JIRA URL
> ----------------------------------
>
> Key: MCHANGES-124
> URL: http://jira.codehaus.org/browse/MCHANGES-124
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira-report
> Affects Versions: 2.0
> Reporter: Vincent Siveton
>
> By default, the maxEntries is set to 100 and the generated JIRA url uses it,
> i.e.:
> {noformat}
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=11138&statusIds=6&sorter/field=issuekey&sorter/order=ASC&sorter/field=issuetype&sorter/order=ASC&tempMax=100&reset=true&decorator=none
> {noformat}
> The Javadoc plugin 2.5 has more than 100 issues but the issues list size
> return by JIRA is 100 without any 2.5 fixVersion!
> A workaround is to increase the maxEntries
--
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
