Project

General

Profile

Forums » Help »

CSV export - what is the point in limiting it to 500 entries?

Added by Sergey Naumov almost 2 years ago

I see that if I use issues.json endpoint, Redmine could export all the issues, but the problem is that it doesn't export fields of plugins (like tags) and export a lot of long but unneeded info (like description) that I can't filter out at the server side.

It looks like everything what I want (filtering, plugin fields) are available in issues.csv endpoint, but the problem is that by default only 500 entries could be exported and there is no pagination to export 1 to 500, then 501 to 1000 and so on. I could ask admins to raise the limit, but the question is why this limit imposed at all?


Replies (2)

RE: CSV export - what is the point in limiting it to 500 entries? - Added by Mohamed El Habchi almost 2 years ago

Redmine export limit is 500 by default which you can change from setting to whatever limit you need
Administration > settings > ticket tracking > Tickets export limit

RE: CSV export - what is the point in limiting it to 500 entries? - Added by Sergey Naumov almost 2 years ago

Hello. Thanks for the answer. Unfortunately, my question is not about how to set the limit, but why it was imposed and why 500 was decided to be a default value.

More broad question is why xml/json endpoints:
  1. support pagination
  2. do not return all fields (say, fields, introduced by plugins)
  3. have a limit of 100 entries per request
  4. do not support requesting just a subset of fields
But at the same time csv/pdf endpoints:
  1. do not support pagination
  2. return all fields, including fields introduced by plugins
  3. have a limit of 500 entries by default (and, as pagination is not supported, it is a total limit)
  4. support requesting a subset of fields

To me it looks like a big inconsistency and it would be good to know what was the reason for it.

    (1-2/2)