Unlink issues from the current issue

A post-function that will unlink issues from the current issue based on the result of a Nunjucks condition.

To add 'Unlink issues from 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 on Post Functions in the properties panel.
Click on Add post function.
Select Unlink issues from the current issue from the list of post-functions.
Click on Add to add the post-function on the transition.
Add a Nunjucks condition in the Condition.
Click on Add to add the post-function to the transition.

Known limitations common to all post-functions:

Related links

For information on where the post-function needs to be placed on a transition, see Placing post-functions in a transition.

Refer to the Use cases for the post-functions page for use cases for this post-function.

Refer the Troubleshooting and Support page if the post-functions does not seem to be working as you would expect.

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 checks the specified condition against each linked issue of the current issue. If the condition evaluates to any text except false or an empty string, it will remove the issue link. If not, it will not remove the link.

Condition

Input a condition in Condition using Nunjucks annotations. You can insert issue, linkedIssue, transition, linkTypeName, currentUser and now variables in your condition and test it using the Nunjucks tester.

Examples:

{{linkTypeName == "blocks"}} returns true for all linked issues linked to the current issue with blocks link type
{{linkedIssue.fields.status.name == "Rejected"}} returns true for all linked issues that are in the Rejected status.

Customize this post-function using the additional options provided as part of the post-function. The options are:

Run As

Run as current user: The current user will be the author of the removal of issue links.

Run as add-on user: The add-on user will be the author of the removal of issue links.

Run as this user: Any user selected in this field will be the author of the removal of issue links.

Delayed execution

Post functions are provided with an option to delay execution for a set number of seconds using the Delayed execution option (Figure 1, right). To delay execution, select the number of seconds to wait until the post-function is run; any value between 1 second (the default) up to a maximum of 20 seconds can be selected.

Workflows that depend on post functions being executed in a specific order can fail due to the asynchronous nature of Connect post-functions in Jira Cloud. One workaround is to delay the execution of a post-function, thereby creating a more predictable execution order. For example, on the approval of a Story you want to create sub-tasks and immediately transition them; in this case, you will have to delay the execution of the Transition Linked Issues post-function, so that the sub-tasks are created before they are transitioned. See the sample use case, below.

Where possible, it is recommended to use the Sequence of post-functions post-function or Shared action post-function to execute a series of post-functions in a specific sequence instead of applying a delay.

Sample use cases for Delayed execution

On the creation of a Bug, assign it to a member of the QA team and then add the Assignee to the Watchers.

Steps

Create a QA project role, with the testers as its members.
Add the Assign to role member post-function to the transition Create of the Bug workflow.
Select QA as the project role to look for.

Add the Copy value from field to field post-function to the Create transition of the Bug workflow.
Select Assignee as the From field.
Select Watchers as the To field.
Select the Delayed execution option and select 5 sec from the Delay drop-down.

On the approval of a Story, create subtasks for Development and QA, and transition them to In Progress status.

Steps

Add the Create issue post-function to the Approve transition of the Story workflow.
Select Same as current issue from the Project field.
Select Subtask from the Issue type field.
Select Current issue from the Parent issue field.
Repeat the above steps for the Development subtask.

Add the Transition linked issues post-function to the Approve transition of the Story workflow.
Select Issue Link Type as is Parent of.
Select the Delayed execution option and select 10 sec from the Delay drop-down.

You are viewing the documentation for Jira Cloud.