https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292014-08-19T18:45:20ZRedmineRedmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=581772014-08-19T18:45:20ZDomingo Galdos
<ul></ul><p>Is there anything I can do to help move this patch forward?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=646292015-07-03T14:22:08ZAnton Statutov
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=647622015-07-10T09:52:57ZV Lindell
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=650672015-07-26T02:08:53ZToshi MARUYAMA
<ul><li><strong>Target version</strong> set to <i>3.2.0</i></li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=650742015-07-26T06:50:15ZGo MAEDA
<ul></ul><p>The user should not be able to set the value of API limit smaller than 100.<br />Probably some clients suppose that the value is always 100, smaller limit may affect compatibility with such clients.</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=674412015-11-22T16:10:49ZJens Peter Kempkes
<ul></ul><p>We would also appreciate higher values than 100. Some of our tools need to load all items visible to a user and therefore need to split the requests.</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=675512015-11-27T07:57:50ZSebastian Paluch
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=676792015-12-06T10:44:31ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Target version</strong> changed from <i>3.2.0</i> to <i>Candidate for next major release</i></li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=677602015-12-09T12:24:52ZJens Peter Kempkes
<ul></ul><p>Too sad, this patch was shifted. <br />What is the reason?</p>
<p>We're really waiting for this patch and all seems to be done. Am I wrong?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=680982015-12-23T10:00:19ZNiklaus Jordi
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=698332016-03-22T11:38:01ZGo MAEDA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/7539">Feature #7539</a>: Rest-API limit of items not 100, but changeable by the administrator</i> added</li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=718242016-06-28T15:54:59ZDam Dam
<ul></ul><p>+1</p>
<p>Hi,<br />This request was posted 2 years ago, so what's up?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=736342016-09-20T07:21:41ZStephane Evr
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=778882017-04-09T00:18:42ZGo MAEDA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/25555">Defect #25555</a>: Make api paging limit configurable</i> added</li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=779112017-04-10T07:55:24ZGeorge Brooke
<ul></ul><p>Is there anything wrong/non-ideal with this patch which means that it has not been integrated?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=789182017-06-01T15:01:19ZBohdan Artemchuk
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=803282017-07-27T15:54:57ZToshi MARUYAMA
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/80328/diff?detail_id=63272">diff</a>)</li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=803312017-07-27T15:55:53ZToshi MARUYAMA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/26553">Feature #26553</a>: Overly restricted number of ReST results</i> added</li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=828552018-01-02T11:57:27ZMichael Gerz
<ul></ul><p>What happened to this patch? Nothing?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=847582018-04-30T06:45:34ZJose Luis Parrilla
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=871532018-09-09T18:35:58ZГордеев Алексей
<ul></ul><p>Silence... :(</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=901842019-02-17T05:15:52ZYuuki NARA
<ul></ul><p>+1</p>
<p>I think that it should be changeable by the responsibility of the system administrator.</p>
<p>There are many configuration items in the world system that may cause troubles due to setting change contents.<br />Since there are cases where it is necessary to change these items, it is made public after clearly stating that there is a risk when changing.</p>
<p>It is enough to specify the following points.</p>
<p>If you change the default value, there is a possibility of trouble in the operation of REST using application.<br />The operation verification responsibility is on Redmine system administrator who changed.</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=904982019-03-01T10:18:36ZC F
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=909852019-03-28T15:43:20ZGianni Cavallotto
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=937772019-09-18T06:03:30Zint redmine
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=943572019-10-16T11:48:08ZMeiki Neumann
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=943612019-10-17T01:34:24Zr okui
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=943622019-10-17T05:44:32ZCédric Berger
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=979972020-05-29T15:40:46ZMischa The Evil
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/33526">Feature #33526</a>: Add possibility to configure limit used to retrieve objects for an API response</i> added</li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=980032020-05-29T16:39:24ZVVD VVD
<ul></ul><p>Russian translation of:</p>
<blockquote>
<p>setting_api_limit: Maximum number of items returned in a JSON/XML API response</p>
</blockquote>
<p>is</p>
<blockquote>
<p>setting_api_limit: Максимальное количество элементов, передаваемых в ответе JSON/XML API</p>
</blockquote> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=982212020-06-15T17:54:33ZVVD VVD
<ul></ul><p>What blocks this change?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=984852020-07-08T14:18:45ZTxinto Vaz
<ul></ul><p>+1</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=986552020-07-27T17:02:58ZVVD VVD
<ul></ul><p>meineerde from IRC #redmine@freenode ask me to describe my use-case.<br />Sorry for my poor english, but I try to explain why this feature is important for me.</p>
<p>We are using Redmine for manage projects - tasks, issues, bugtracker. 10-20 active projects with hundreds active issues and 100+ active users - employees and customers. Employees are using "Spent time" in issues to record work time for every issue every day. The employees' salary depends on those records.<br />We have developed application on Java+Tomcat for create reports with values from "Spent time" fields. It using REST API to get values:<br /><pre>http://redmine.host/time_entries.json?spent_on=><BEGIN_OF_MONTH|END_OF_MONTH&offset=N&limit=10000</pre><br />For example to get 20000 objects - 200 requests in ~3 minutes even on localhost. But it's faster with limit 10000 - ~20 seconds only.<br />After end of each month 10+ project managers (I'm one of them) using this application to create reports for each project. The employees salary calculated from this reports. Every mouth we have thousands of "Spent time" entries. It's too long for users wait several minutes for "simple" report, and even more - some browsers timedout connection during this time…</p>
<p>Please, commit this patch!</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=995352020-10-24T08:02:35Zvzvu 3k6k
<ul><li><strong>File</strong> <a href="/attachments/26113">0001-domingo-galdos.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/26113/0001-domingo-galdos.patch">0001-domingo-galdos.patch</a> added</li><li><strong>File</strong> <a href="/attachments/26114">0002-add-test.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/26114/0002-add-test.patch">0002-add-test.patch</a> added</li><li><strong>File</strong> <a href="/attachments/26116">0003-move-to-api-tab.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/26116/0003-move-to-api-tab.patch">0003-move-to-api-tab.patch</a> added</li><li><strong>File</strong> <a href="/attachments/26115">0004-simplify-label.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/26115/0004-simplify-label.patch">0004-simplify-label.patch</a> added</li><li><strong>File</strong> <a href="/attachments/26117">0005-quickfix-allow-less-than-25.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/26117/0005-quickfix-allow-less-than-25.patch">0005-quickfix-allow-less-than-25.patch</a> added</li></ul><p>Looks good. We've wrote a patch based on Domingo Galdos' one (Patch 0001) with Juno NISHIZAKI, sanak and me on Redmine patch meeting 4th.</p>
The changes are as follows:
<ul>
<li>Added a test. (Patch 0002)</li>
<li>Moved the configuration value form from the "General" tab to the "API" tab and shorten the label name. (Patch 0003, 0004)</li>
<li>In the current implementation, if the limit parameter is less than 1, Redmine sets limit to 25. the limit is less than 25, the conditional statement is modified to be replaced by another one. (Patch 0005)</li>
</ul>
<p>Go MAEDA wrote:</p>
<blockquote>
<p>The user should not be able to set the value of API limit smaller than 100.<br />Probably some clients suppose that the value is always 100, smaller limit may affect compatibility with such clients.</p>
</blockquote>
<p>Sounds reasonable, but currently the setting page doesn't have any validations. Do you have any good idea to apply the constraint?</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=995522020-10-26T07:10:27ZMizuki ISHIKAWA
<ul><li><strong>File</strong> <a href="/attachments/26119">Add-validation-to-api-limit.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/26119/Add-validation-to-api-limit.patch">Add-validation-to-api-limit.patch</a> added</li></ul><p>vzvu 3k6k wrote:</p>
<blockquote>
<p>Go MAEDA wrote:</p>
<blockquote>
<p>The user should not be able to set the value of API limit smaller than 100.<br />Probably some clients suppose that the value is always 100, smaller limit may affect compatibility with such clients.</p>
</blockquote>
<p>Sounds reasonable, but currently the setting page doesn't have any validations. Do you have any good idea to apply the constraint?</p>
</blockquote>
<p>The attached patch adds validation, though it may not be the best way to write it.</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=995582020-10-26T21:05:54ZMarius BĂLTEANU
<ul><li><strong>Target version</strong> changed from <i>Candidate for next major release</i> to <i>4.2.0</i></li></ul><p>The final result of the patch series posted by vzvu 3k6k and Mizuki looks good to me and all the tests pass: <a class="external" href="https://gitlab.com/redmine-org/redmine/-/pipelines/207877707">https://gitlab.com/redmine-org/redmine/-/pipelines/207877707</a></p>
<p>I propose to evaluate this for 4.2.0, but we should have Jean-Philippe agree on this because he rejected the patch some time ago. The feature is useful, for sure.</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=1014062021-03-17T17:11:53ZRoberto Mendes
<ul></ul><p>I need this. To get more than 100 items.</p> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=1015052021-03-23T20:42:53ZMarius BĂLTEANU
<ul><li><strong>Target version</strong> changed from <i>4.2.0</i> to <i>5.0.0</i></li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=1059762022-03-18T18:43:36ZMarius BĂLTEANU
<ul><li><strong>Target version</strong> changed from <i>5.0.0</i> to <i>Candidate for next major release</i></li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=1091542023-01-21T07:56:14ZGo MAEDA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/38173">Feature #38173</a>: Increase limit of entries in json/xml and, preferably, make it configurable</i> added</li></ul> Redmine - Patch #16069: Allow configuration of API limit instead of hardcoding at 100https://www.redmine.org/issues/16069?journal_id=1102422023-06-15T07:56:14ZMaciej Czechowicz
<ul></ul><p>Is it possible to push this request? I have application which sends 13 requests to Redmine and takes internity for that.</p>