-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Component/s: Dashboard - Dashboards & Gadgets
-
14
-
Severity 3 - Minor
-
4
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
- 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.
- As an example, add the Two Dimensional Filter Statistics gadget to your Dashboard and use that saved filter you've just created
- 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.
- is duplicated by
-
JRACLOUD-80076 Request too large for Dashboard gadget with too many issue keys
-
- Closed
-
-
JRACLOUD-83196 Navigating Dashboard Gadget issues with extended JQL results in "Requested URL too large" error
-
- Closed
-
- is related to
-
JRACLOUD-84160 Jira dashboard gadgets build generate search as raw JQL causing 413 error
- Closed
- is resolved by
-
JDAG-1390 Loading...