-
Bug
-
Resolution: Duplicate
-
Low
-
2
-
Severity 3 - Minor
-
1
-
Issue Summary
JQL searches that include the issueLinkType field may not work depending on the amount of issues and links that exist.
Environment
Cloud
- This behavior does not change between the new and old issue view
Steps to Reproduce
Although this problem does not occur always, it may happen in instances with a considerably high amount of issues (i.e. 300k+ issues).
- To replicate, run a simple search containing the issueLinkType field
- Example: issueLinkType is not EMPTY
Expected Results
Search returns issues that match search criteria
Actual Results
An error saying "An unknown error occurred while trying to perform a search."
A failed request with a response code of "JQL too complex" may be returned in the Browser's console
Workaround
Limiting the search criteria may be a valid workaround.
- Example: project = <Project A> and issueLinkType is not EMPTY
In case that search does not work, it is possible to try a different approach:
- Create a filter filter like: issueLinkType is EMPTY;
- Perform the search like the following: project = <project> AND filter != "filter"
- duplicates
-
-
- Closed
-
- is cloned from
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-77619] Issue searches containing "issueLinkType" may not work depending on the amount of existing links
I believe this issue is a duplicate of JRACLOUD-73640 – JQL issueLinkType is inconsistent when using != or NOT IN operators
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!
As per this comment I am closing this ticket.
If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.