Failed Exports when Query Is Too Long

Some users have started experiencing an issue where they receive the following error after attempting to export using templates:

The JIRA logs show contain the text attached here: excerpt.log

org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)

While troubleshooting, we have found that this error appears to be occurring based on the length of the JIRA query, rather than the length of a field value in the issues.  For example, this query causes an error:

project = ABC AND issuetype in subTaskIssueTypes() AND status in (Open, "In Progress", Reopened, "Internal Pending", "External Pending", "In Review", Suspended, "Ready for Test", Executing, "Ready to Execute") AND Sprint = 3243 ORDER BY assignee ASC

Note the large amount of statuses.  I was able to get the export to work by inverting that portion, which shortens the query a good bit:

project = ERC AND issuetype in subTaskIssueTypes() AND status not in (Resolved, Closed) AND Sprint = 3243 ORDER BY assignee ASC

This filter results in the same issues, but is more efficient as it shows all but the only two statuses not referenced in the first query.

We have discovered that the query used for an export is stored in the database, which combined with the workaround we found, leads us to believe that the problem is the character limit in that database column.

2018-02-07 12:01:49.518 | {"JQL":"project \u003d ABC AND issuetype in subTaskIssueTypes() AND status not in (Resolved, Closed) AND Sprint \u003d 3243 ORDER BY assignee ASC","Filter":""} |
.xlsx     | 48 | xlsx          | 52474eaf49d54035ba27676250f8b831     |              100 | FINISHED       |       35 | MULTI_ISSUE     | joseph.otis

That JQL was stored in the DETAILS column of our "AO_3C6513_XPORTER_PROCESS" table.  The query that caused the error was 250 characters long, but with the extra text added with "{"JQL":"" and "","Filter""}", that exceeds the column's 255 character limit.