linkedIssuesOfRecursiveLimited

The linkedIssuesOfRecursiveLimited function extends the capabilities of linkedIssuesOfRecursive by adding a critical feature: the ability to limit the depth of the issue link traversal. This applies when understanding dependencies beyond a certain depth becomes less relevant or could clutter the analysis with excessive information.

It is particularly beneficial for:

Focusing on immediate or near-term dependencies that are most relevant
Providing clearer, more manageable insights into dependencies

Syntax and parameters

linkedIssuesOfRecursiveLimited(Subquery, Traversal depth, [Link name])

Subquery: A JQL query string that identifies the initial set of issues. This query is enclosed in double quotes.
Traversal depth: An integer specifying how many levels deep the function should traverse issue links.
Link name: Specifies the type of issue link to consider in the traversal.

linkedIssuesOfRecursiveLimited demo video

Examples

Limiting dependency analysis to immediate links:
To explore all links from issues in the DEMO project, limited to two links deep:
1
```
issueFunction in linkedIssuesOfRecursiveLimited("project = DEMO", 2)
```
This query helps project managers focus on the most immediate dependencies that could impact the project's short-term goals.
Specifying link types for targeted analysis:
For a targeted approach, specifying a link type narrows down the analysis:
1
```
issueFunction in linkedIssuesOfRecursiveLimited("issue = TEST-2", 3, "is blocked by")
```
This would return issues like TEST-3, TEST-6, and TEST-5, providing insight into the specific obstacles facing TEST-2.

Note:

Choose an appropriate depth: Selecting the right depth for traversal can significantly impact the usefulness of the results. Consider the complexity of your project and the level of detail needed when deciding.

Combine with specific link types: Utilising the optional link type parameter can yield more focused insights, especially when dealing with large projects or when certain dependencies are of particular interest.

The following query will follow all links, recursively, from all issues in the DEMO project until it has traversed a maximum of 2 links deep along any link path.

issueFunction in linkedIssuesOfRecursiveLimited("project = DEMO", 2)

Using the following setup:

Our query with the depth parameter would return: DEMO-1, DEMO-2, TEST-1, TEST-2, TEST-4 and TEST-5.

We could specify the link name as well, to get different results:

issueFunction in linkedIssuesOfRecursiveLimited("issue = TEST-2", 3, "is blocked by")

which would return: TEST-3, TEST-6 and TEST-5