Advanced Link Query Options | OBSS Apps Documentation

Linked Issue Query Function

SearchMate adds an extended search function that allows you to list issues based on their linked relationships. The function works directly inside the Jira Issue Navigator and uses your JQL input to identify which work items should be included in the results.

SearchMate automatically interprets link types and link directions. This means inward and outward definitions are handled internally, and all supported link types are evaluated consistently.

The following example shows how the function is used in the Advanced Search screen:

issueKey in linkedItemsFromQuery(<jql>, <linkNameOrLinkId>, <LinkDirection>)
For example: issueKey in linkedItemsFromQuery("project = BUG", "Blocks", "inward")

 issueKey in linkedItemsFromQuery("project = BUG", "Blocks", "inward")

Parameter	Required(Yes& No )	Description
JQL	Yes	issues returned by the base JQL query. Since no link type is specified, all link types and both directions (inward/outward) are included.
Link name or link id	No	Returns only the issues linked with the Blocks link type. Link direction is automatically resolved, so both blocks and is blocked by relationships are included.
Link direction	No	Returns only the issues that have an inward Blocks relationship to the results of the base JQL. Direction is explicitly defined, so only is blocked by connections are returned.

This queries work in two steps:

1. Running the base JQL query

The text inside the quotation marks is executed first.
In this example, "project = BUG" returns all work items in the BUG project.

2. Finding linked work items

SearchMate then examines the links of those items and returns all issues connected through the Blocks link type.
Link direction does not affect the result. Both “blocks” and “is blocked by” are included automatically.

When the search is executed, the results appear in the standard Issue Navigator. The Linked work items column shows the items identified through the relationship check, allowing you to see the connection paths without opening individual issues.The Linked Work Items column is not shown by default; you need to add it manually.

SearchMate follows Jira’s native permission model. Users only see issues they already have access to, ensuring safe and consistent relationship-based searches across projects.

Nested SearchMate functions (up to 2 levels)
SearchMate also supports using the same function nested inside itself, up to two levels.
In this case, the inner function is evaluated first, and the outer function works on the result of the inner one.

Example

issueKey in linkedItemsFromQuery(
  "issueKey in linkedItemsFromQuery(\"issueKey = FB\")"
)

The inner linkedItemsFromQuery("issueKey = FB") returns all issues linked to the issue with key FB.
The outer linkedItemsFromQuery(...) then takes that result set and returns all issues linked to those issues.

Cross-function nesting is NOT supported

SearchMate only allows nested usage of the same function.

Mixing different SearchMate functions inside each other is not allowed, and will produce an error during execution.

Unsupported example:

issueKey in linkedItemsFromQuery(
"project = TS AND issueKey in linkedItemsFromFilter(\"issueKey = FB\")"
)