Link issues to the current issue
A post-function that will link the current issue to all issues that satisfy a parameterized JQL query.
To add 'Link issues to the current issue' post-function to a transition:
Click Edit for the workflow that has the transition you wish to add the post-function on.
In the Workflow Designer, select the transition.
Click Post Functions in the properties panel (or select the Post Functions tab).
Click Add post function.
Select Link issues to the current issue from the list of post-functions.
Click Add. The Link issue fields to the current issue screen will open, where you can configure the post function as needed. See below for more details on specific configurations.
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.
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.
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 TESTassignee is EMPTY
returns all the unassigned issues.project=TEST order by created desc
returns the issues of the project whose key isTEST
in descending order byCreated
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 thetargetIssue
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 withsummary ~ "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
Run As
Conditional execution
Delayed execution
On this page |
---|