You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2015/01/26 23:11:34 UTC
[jira] [Commented] (INFRA-9069) Raise JIRA's maxEntry search limit
on REST API
[ https://issues.apache.org/jira/browse/INFRA-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292500#comment-14292500 ]
Geoffrey Corey commented on INFRA-9069:
---------------------------------------
Please see [NFRA-9059] on why the limit will not be raised.
> Raise JIRA's maxEntry search limit on REST API
> -----------------------------------------------
>
> Key: INFRA-9069
> URL: https://issues.apache.org/jira/browse/INFRA-9069
> Project: Infrastructure
> Issue Type: Wish
> Components: JIRA
> Environment: ASF JIRA
> Reporter: Bernd Eckenfels
>
> When using the maven-changes plugin to collect Bug informations for a Project about to be released (Commons VFS) I noticed, that the plugin does not yet allow to page through the result set.
> I opened http://jira.codehaus.org/browse/MCHANGES-351 for this, however it looks like this takes some time. I wonder if it is possible to raise the rather low default on the ASF JIRA to 150 or 300 for the limit. I think this is done with the `jira.search.views.max.limit` parameter. (For the release I would actually need 149 entries, but I guess a more general solution would be allow some more. I think JIRA-on-demand for example sets it to 1000).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)