Delete issue(s)

A workflow post-function that deletes one or more issuesTo add the 'Delete issue(s)' 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 Delete issue from the list of post-functions.
Click on Add to add the post-function to the transition.
Select the “Target issue” (see below)
Click on Add to add the post-function to the transition.

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

When you add this post-function to a transition and trigger the transition, the add-on deletes the target issues.

Issue(s) to operate on

Select the issues to be deleted. They can be:

Current issue: Select this option to delete the current issue. This is the default option.
Sub-tasks of the current issue: Select this option to delete the sub-tasks of the current issue
Parent issue of the current sub-task: Select this option to delete the parent of the current issue. Note the subtasks of the parent are also deleted.
Issues that belong to the current issue (Epic): Select this option to delete the issues that belong to the current Epic
Epic of the current issue: Select this option to delete the Epic of the current issue
Child issues of the current issue in the Portfolio hierarchy: Select this option to delete the child issues of the current issue in the Portfolio hierarchy
Parent issue of the current issue in the Portfolio hierarchy: Select this option to delete the parent issue of the current issue in the Portfolio hierarchy
Issues linked to the current issue through any link type: Select this option to delete all issues linked to the current issue
Issues linked to the current issue through the following link type: Select this option to delete the linked issues of a specific link type. Select the specific link type under “Issue link”
Issues returned by the following Nunjucks template: Select this option to delete the issues returned by the result of a Nunjucks template. Input a Nunjucks template which is a comma-separated list of valid issue keys. For example:
- "TEST-1"
- "TEST-1","TEST-2"
- {{ issue.fields.parent.key }}
- {{ issue.fields.subtasks | join(",", "key") }}
Issues returned by a JQL search: Select this option to delete the issues returned by a JQL search. Input a JQL search expression. For example:
- project = TEST returns issues of the project with the key TEST
- project = {{ issue.fields.project.key }} and assignee = {{currentUser._accountId}} returns issues of a project that belong to the project with key TEST and the assignee is the current user
- ```
{% if issue.fields.assignee %}
    assignee = {{issue.fields.assignee._accountId}}
{% else %}
    issuekey=INVALID-1
{% endif %}
```
  Note that the {% if %} block is necessary to avoid an invalid JQL query when the issue is unassigned. In that case, the template will return a valid JQL query that returns no issue (issuekey=INVALID-1).

Run As

Run as current user: The current user will be the user that deletes the new issue.

Run as add-on user: The add-on user will be the user that deletes the new issue.

Run as this user: Any user selected in this field will be the user that deletes the new issue.

Conditional execution

To execute this post-function based on the result of a Nunjucks template see Conditional execution.

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.