Use POST to export Issue query results to CSV instead of GET
When trying to export issues to CSV, all request params (filter settings) are sent in the URL via a GET request. For an issue filter with lots of params using non-latin characters it is quite easy to hit the 8190 byte URL length limit for apache2.
I suppose it'd be better to send POST requests with params sent as request body thus allowing to manage larger amounts of data.
#1 Updated by Go MAEDA over 5 years ago
- Category set to Issues filter
I am against this (I usually use non-latin characters, Japanese).
If this feature is implemented, we will not be able to tell the URL of filtered issues list via email or chat like this:
#2 Updated by Jens Krämer over 4 years ago
I think the OP is using a saved query and just has the problem that the modal CSV export options form serializes the query (even if it is a stored query) into a bunch of hidden fields for filters and options etc. If the modal would instead just use a hidden
query_id field he wouldn't have the problem. Or if the options form in the modal (and just this) would use POST.