/
Link issues to the current issue

Link issues to the current issue

A post function that will link the current issue to all issues that satisfy a parameterized JQL query.

When you add this post function to a transition and trigger it, the add-on links the current issue to the specified number of issues that satisfy the specified parameterized JQL query.

MultiExcerpt Include

JMWE shows an error message on the issue view if any error occurs during the execution of the post function. This message is displayed only if the current user is a Jira administrator. 

Link Issues to the Current Issue configuration screen
Figure 1 - Link issues to the current issue

Issues to link

  • JQL Filter - Input a JQL expression that returns the issues to link to the current issue. You can insert issue, transition, currentUser and now variables in your JQL expression and test it using the JQL expression tester provided in this post function.

    Examples:

    • project = TEST returns the issues of the project whose key is TEST

    • assignee is EMPTY returns all the unassigned issues.

    • project=TEST order by created desc returns the issues of the project whose key is TEST in descending order by Created time

To specify a condition on a user, you need to specify an accountId without the accountId: prefix. For example: assignee = 557058:472c64c9-2567-4213-839b-86bf21558300. You can access the prefix-less accountId of a user through the _accountId property.

Note: If the current issue satisfies the specified JQL query, an error is logged because you cannot link an issue with itself.

Examples:

project = {{ issue.fields.project.key }} and assignee = {{currentUser._accountId}}
{% if issue.fields.assignee %} assignee = {{issue.fields.assignee._accountId}} {% else %} issuekey=INVALID-1 {% endif %}

You can find more information about searching for Jira issues using JQL here: Advanced searching and Search Jira like a boss with JQL.

  • Max. Issues - Input the maximum number of issues that the JQL expression should return. The value cannot be more than 50.

  • Nunjucks condition - Select this option to filter the issues returned by the JQL search. Input a Nunjucks template in the Filter Expression that returns true if the issue returned by the JQL search should be linked to the current issue. The filter script is evaluated for each issue returned by the JQL search, in turn, and that issue is available through the targetIssue variable. This is especially useful when you want to filter linked issues that cannot be filtered using the JQL.

    For example, filtering issues refining a text search with an exact match that cannot be done with JQL. For example to check for issues with summary ~ "MacBook Pro" the JQL returns all issues with “MacBook” and “Pro” in the summary (say, “MacBook for Pro users”). In such a case, you should be using the “Filter Expression” to filter issues that have “MacBook Pro” in the summary with a Nunjucks template as follows:

{{ issue.fields.summary.includes("MacBook Pro") }}

Link type

  • Issue Link Type - Select the link type to be created between the current issue and the issues returned from the JQL expression.

Advanced options

Expand this section to see advanced configurations including which user will run the post function, conditional execution, and delayed execution.

Run As

Conditional execution

Delayed execution