Versions Compared
Version | Old Version 3 | New Version Current |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Excerpt |
---|
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 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 on Post Functions in Functions in the properties panel (or select the Post Functions tab).
Click on
Add
post Add post function.Select Link issues to the current issue from the list of post-functions.
Click on Add to add the post-function on the transition.
Add a JQL query in the
JQL expression
.Select the maximum number of issues in
Max. Issues.
Select the link type from the
Issue Link Type
drop-down.Click on
Add
to add the post-function to the transition. 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.
Info |
---|
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
Note: If the current issue satisfies the specified JQL query, an error is logged because you cannot link an issue with itself.
Note that toInfo |
---|
To specify a condition on a user, you need to specify an accountId without the accountId: prefix. For example: |
Note |
---|
Note: If the current issue satisfies the specified JQL query, an error is logged because you cannot link an issue with itself. |
Examples:
Code Block | ||
---|---|---|
| ||
project = {{ issue.fields.project.key }} and assignee = {{currentUser._accountId}} |
Code Block | ||
---|---|---|
| ||
{% 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:
Code Block |
---|
{{ 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
Include Page |
---|
Run as current user: The current user will be the creator of the issue links.
Run as add-on user: The add-on user will be the creator of the issue links.
Run as this user: Any user selected in this field will be the creator of the issue links.
Conditional execution
To execute this post-function based on the result of a Nunjucks template see Conditional execution. The condition is evaluated only after the JQL query runs and not before. It will be evaluated against each issue returned by the JQL query allowing you to further filter the issues to link to the current issue. The issues returned by the JQL query will be available in your Nunjucks template through the linkedIssue variable.
|
Conditional execution
Include Page | ||||
---|---|---|---|---|
|
Delayed execution
Include Page | ||||
---|---|---|---|---|
|
You are viewing the documentation for Jira Cloud.
On |
---|
this page
|
---|
|
---|
|
---|

