-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
7.13.9, 8.5.4
-
7.13
-
1
-
Severity 3 - Minor
-
Issue Summary
When Two Dimensional Filter is configured with Epic Link on an axis and using a filter that has issuetype the generated JQL includes an additional issuetype check.
Steps to Reproduce
- Create filter to include issuetype != Epic
- Add Two Dimensional Filter gadget and select Epic Link as one of the axis.
- Select the hyperlink for any Epic Link entry
Expected Results
Filter created for test project = BST AND status not in (Resolved, Closed, Done) AND issuetype != Epic
The expected JQL created is expected to use the filter and add the additional search criteria of the second filter. In the case of selecting all issue with Epic Link BST-501 we expect the search query to be
project = BST AND status not in (Resolved, Closed, Done) AND issuetype != Epic AND "Epic Link" = BST-501
Actual Results
The JQL query generated repeats the project check and issuetype but using an in against the already not in.
project = BST AND status not in (Resolved, Closed, Done) AND issuetype != Epic AND project in (10000) AND issuetype in ("10200", "10002", "10101", "10001", "10100", "10103", "10400", "10004", "10003", "10102", "10300", "10006", "10401", "10005", "10104") AND cf[10100] = BST-500
The result of adding in the duplicated search criteria results in customer query exceeding 10,000 characters when they have a large number of issuetypes which fails their maximum URL length.
Workaround
The only workaround is to not use issuetype in the filter if Epic Link is to be used as an axis in the gadget display.
In the case of the customer they wish to exclude Epics from the returned data so the workaround is invalid.
- mentioned in
-
Page Loading...