linkedIssuesOf search - Possible to select for Parent Link (not the "is Parent of" linkage?

[jhochhei]

When searching using linkedIssuesOf is it possible to select for the Jira Parent Link field?  Doing some experimenting there are entries in the Linked Issue types that read as the Parent Link, however it does not appear to be treated as the same in the search.

When viewing our Features in Jira issues linked via the Linked Issue type show in a group under the Issue Links header and there is a separate group/header for user stories linked via the parent link option )with the heading above a separate grouping of user stories (labeled as child issues)

I have tried using the similar sounding link descriptions but they do not provide the results of the Parent Link.

[Crystelle S]

There is also the [parent link] field that is offered as part of the Advanced Roadmaps laddering paradigm. I believe the poster is hoping to use this but is unsure of how it is recorded in the backend. Just as Epic Link is recorded in a pair in the backend and can be called by LinkedIssuesOf, I believe (and it is my query as well) the poster is asking for the same on Parent Link.

[PD Sheehan]

There are 3 very different types of relationships between issues that I can think of right now and I'm not clear which you mean since you are using terminology from all of them.

1. issue links: these are bi-directional. Either "inward" or "outward". Issues on both sides of the link are at the same level (not parent/child)
2.  issue/subtask : the issue is the parent, the subtask (as determined by the issue type) are the children
3. Epic/Stories : this is a special type of links managed by Jira Sofware. It behaves more like issue/subtask, but the parent and child terminology don't apply. 

So, the scriptrunner JQL functions for each of those situations are, respectively:

1. linkedIssuesOf() (and it's variants like linkedIssuesOfAll() etc (and jira built-in linkedIssues()
2. subTasksOf() /parentsOf()
3. issuesInEpics() / epicsOf()