Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-80076

Request too large for Dashboard gadget with too many issue keys

      Issue Summary

      When using the any gadget in Dashboard, it is not recommended to use a saved filter that uses purely issue keys as its JQL because if there are too many issue keys in the query then the request will be too large and cause it to break.

      Steps to Reproduce

      1. Create a saved filter using only issue keys ("key in (PKEY-1, PKEY-2, PKEY-3, PKEY-4)"). This was tested with 600 issue keys and above.
      2. As an example, add the Two Dimensional Filter Statistics gadget to your Dashboard and use that saved filter you've just created
      3. Click on the highlighted number count to view the results of the XAxis or YAxis field selected.

      Expected Results

      You will be redirected to a new tab displaying the results based on the XAxis or YAxis field used.

      Actual Results

      414 Request-URI Too Large
      

      Workaround

      The saved filter must be adjusted to use field references for its JQL and not purely use issue keys.

            [JRACLOUD-80076] Request too large for Dashboard gadget with too many issue keys

            No work has yet been logged on this issue.

              Unassigned Unassigned
              6048cd401523 Felipe Oliveira
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: