Versions Compared

Old Version 1

changes.mady.by.user Mariia Romanova

Saved on

compared with

New Version Current

changes.mady.by.user David Ortiz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are three JQL functions supported by the add-on:

...

...

  • LinksHierarchyFilter

...

  • LinksHierarchyVersion

...

Note

Note

TheJQL functions are continuously optimized to obtain the best performance in terms of response times.

The runtime of the jqls depends on 3 factors:

  1. The number of issues for which the hierarchy must be built.

  2. The depth of the hierarchy to be obtained.

  3. The number of links that have the issues present in the hierarchy.

You should keep in mind that the greater these factors are, the greater the amount of information that will have to be analyzed, especially with the linksHierarchyFilter and linksHierarchyVersion.

For this reason, we recommend using the jql functions always applying filters(exclusions) to limit the amount of information to analyze and improve response times.

Note

We have mentioned the 3 factors that affect the response time of JQL functions.
These factors increase significantly when JQL functions are used recursively. We do not recommend its use.
Take care with recursive searches in your JQL, as they can cause issues with your Jira instance, slowing it down.

Image Modified

All of them work in the same way:

...

By default, the JQL function shows the first depth only. You can filter the results by setting some optional parameters:

...

DEMO-5 (Story) and DEMO-10 (New feature). When the JQL function builds the tree, it founds the DEMO-5 and it will stop to load that branch because the DEMO-5 issue type (Story) has been included in the filter. Therefore the DEMO-1 and the DEMO-6 which are children of the DEMO-5 issue will be ignored as well as their children, and so on.

...

...