Details
-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
25
-
Severity 3 - Minor
-
5
-
Description
Summary
Searching for the "Parent Link" field using the "IS EMPTY" or "IS NOT EMPTY" operators returns wrong results.
Steps to Reproduce
- While having Advanced Roadmaps active do the following search
"Parent Link" is not EMPTY
Expected Results
The search should only return issues that have a value for the Parent Link field.
Actual Results
The search return issues without a value for the Parent Link field.
When using the "IS EMPTY" operator the search result excludes issues that don't have a value for the Parent Link and should appear.
Workaround
Parent Link is not EMPTY considers 3 types of "parent links": Parent Link from Advanced Roadmaps, Epics and subtasks. To search issues with only the Parent Link custom field present, exclude the other possible links:
"Parent Link" is not EMPTY AND "Epic Link" is EMPTY
And to further exclude subtasks, if needed:
"Parent Link" is not EMPTY AND "Epic Link" is EMPTY AND issuetype in standardIssueTypes()
Quick fix :
- For those issues not return the correct result. Check their history.
- Convert it from epic or higher -> other standard types( bug, task, story) and then convert it back
- You may lose the children links but you could relink them by retrieving the issue history
Notes
Other searches for specific results seem to be working normally. Searches using the IN operator work fine as well.
In case you are using the workaround but the "Parent Link" column is not being populated with the issue key, then make sure that you have permissions on the project where the Parent issue is in.
Attachments
Issue Links
- is related to
-
JSWCLOUD-19744 Make "Parent Link" support "is EMPTY" in JQL
- Closed
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
JPO-22986 Loading...
- was cloned as
-
- Gathering Interest
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-