Page Comparison

In general, the pool of issues available for selection is determined by the field’s context.

Further down, it can be narrowed down by additional filtering using a JQL query.

Apart from the default JQL syntax, we provide custom JQL functions to allow even more control of the results.

Issue in relation

This JQL function helps find all your issues within certain relations. It would be best to explain the function's logic using an example.

An employee profile issue has an Advanced Link field ‘Hardware’. It is required to configure selectable issues for this field.

The options available for selection should be displayed only if they are selected in another Advanced Link field ‘Assets'.

The JQL for such scope will appear as follows:

issue in relation("issuetype = Hardware", "Organisation - Assets", "level1")

This expression will return all the issues that are selected in the advanced link fields ‘Organisation - Assets’, both outward and inward. An additional parameter, "issuetype = Hardware" has been added to narrow down the issues by type. "level1" parameter indicates that only issues selected directly in the field will be returned.

Overall, the issue in relation to function has the following structure:

issue in relation("JQL filter", "Advanced LinkField name", "Link level")

where the 3 parameters are interpreted as:

"Advanced Link nameOutward/Inward" (required)- full name of the Advanced Link configurationoutward or inward advanced link field.

"Link level" (required) - currently extends to levels 1 & 2. When querying for level 2, the query will also return issues linked to issues from level 1.

"JQL filter" (optional) is applied to the issues additionally , e.g. ‘status = Active’.

Currently ‘issues in relation’ doest does not support the ‘not’ JQL operator.

This function is applicable only in the Advanced link configuration. It can not be used for JQL search.

JQL Variables

The variables below can be used for data logic configuration for both, Advanced Links and Issue Filter panels.