Vote #67029
未完了Need a way to load all issues in 1 web request, not just 25/50/100
0%
説明
I'm trying to use Excel<-Redmine import feature I described in task #5284.
Another problem I see is that "# of issues per page" parameter is not saved in user settings and also can't be more than 100.
I tried query
http://
but it seems all "per_page" values are ignored except for "25, 50, 100".
As the result, the Excel<-Redmine import can only load and automatically update first 25/50/100 rows while I need to see ALL tasks there.
I know I can export issues from redmine to a CSV file, but this is less convenient for automatic updates for the imported data in Excel.
I understand a heavy query can add some load to the server, but I don't think this is a big issue in my circumstances.
Any help?
journals
Check your Redmine settings. In your Settings -> General you have the "Objects per page options" where you can add your own definition. By adding (for instance) 5000 there would make you able to get that many results into Excel.
--------------------------------------------------------------------------------
Indeed.
--------------------------------------------------------------------------------
Thanks, guys. I didn't know that.
--------------------------------------------------------------------------------
*Need a way to load _all_ issues in 1 web request, not just 25/50/100/any_other_finite_number*
Could it be possible to add "all" option?
There could be a checkbox to enable that or something like:
<pre>
Objects per page options: 25, 50, 100, 200, all
Multiple values and string "all" allowed (comma separated)
</pre>
Changing "Objects per page" maximum value is a workaround and doing this whenever someone needs a bigger max-value(issues quantity grows through time) implies that he must contact redmine admin.
--------------------------------------------------------------------------------
I haven't used REST APIs much, but I have yet to stumble across one that didn't paginate… Any particular reason you aren't happy with the paginated results other than "oh god I have to make more than one request that's too complicated :-O"?
--------------------------------------------------------------------------------
Felix Schäfer wrote:
> I haven't used REST APIs much, but I have yet to stumble across one that didn't paginate… Any particular reason you aren't happy with the paginated results other than "oh god I have to make more than one request that's too complicated :-O"?
you're right, i am just lazy:)
But it is not for REST API, i'm talking about browser view:
for example a manager wants to see some statistics, he configures filters, grouping and columns as he need and.. he can not see results in one place because of limited issues per page.
--------------------------------------------------------------------------------
I think this request's priority can be set to "LOW".
--------------------------------------------------------------------------------
Closing this as it's old and has no feedback since 2 years.
--------------------------------------------------------------------------------
表示するデータがありません