Sequence of Post-functions

For example, consider that during a transition you need to first create a new issue (using the Create Issue(s) post-function) and then send a notification email mentioning the new issue (using the Email Issue post-function). In this scenario, you need to make sure that the first post function has finished running before starting the second, which is something that Jira Cloud doesn't guarantee if you don't use a Sequence of post functions post function.

To add the 'Sequence of Post-functions' post function to a transition: 

1. Click Edit for the workflow that has the transition you wish to add the post-function on.

2. In the Workflow Designer, select the transition.

3. Click Post Functions in the properties panel.

4. Click Add post function.

5. Select Sequence of Post-functions from the list of post functions.

6. Click Add to navigate to the Create issue(s) post-function screen where you can add configuration details to the post-function. See below for configuration details.

7. Click Add to add the post-function to the transition.

After adding the post function, move it to the appropriate position according to Placing post functions in a transition.

Issue(s) to operate on

Select the issues on which the sequence of post-functions should be run.

• Target issue(s)

  • Current issue - Select this option to run the sequence of post-functions on the current issue. This is the default option.

  • Sub-tasks of the current issue - Select this option to run the sequence of post-functions on the sub-tasks of the current issue

  • Parent issue of the current sub-task - Select this option to run the sequence of post-functions on the parent of the current issue

  • Issues that belong to the current issue (Epic) - Select this option to run the sequence of post-functions on the issues that belong to the current Epic

  • Epic of the current issue - Select this option to run the sequence of post-functions on the Epic of the current issue

  • Child issues of the current issue in the Portfolio hierarchy - Select this option to run the sequence of post-functions on 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 run the sequence of post-functions on 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 run the sequence of post-functions on all issues linked to the current issue

  • Issues linked to the current issue through the following link type - Select this option to run the sequence of post-functions on 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 run the sequence of post-functions on 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"
{{ targetIssue.fields.parent.key }}
{{ targetIssue.fields.subtasks | join(",", "key") }}

  • Issues returned by a JQL search:  Select this option to run the sequence of post-functions on 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 = {{ targetIssue.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 targetIssue.fields.assignee %} assignee = {{targetIssue.fields.assignee._accountId}} {% else %} issuekey=INVALID-1 {% endif %}

Post-functions

Open

Figure 2 - Included post function

Create the ordered list of post functions to be run against the selected issue. The following controls are available:

• Click Add post function to add a post function to the list.

• To reorder post functions, use the handle ( ) to drag and drop a post function to its new position in the order.

• Click Caret ( )to show or hide a post function’s configuration.

  • Click Edit ( )to edit the post function configuration.

  • Click Remove ( ) to completely remove a post function from the sequence.
    Note: this cannot be undone!

Error handling

Skip subsequent post-functions if a post-function encounters an error - By default, even if one of the post functions fails with an error, the remaining post functions in the sequence will still run. Select this option to stop the execution of subsequent post functions after an error occurs.

Conditional execution

Delayed execution

Passing variables within a sequence

By using the {% setContextVar %} Nunjucks tag you can pass data from one post function to a subsequent post function.

context: Holds all the context variables added in the current post-function. For example, if you create a context variable myVar in the first post-function of the sequence:

This variable will then be available to subsequent post-functions as:

Variables specific to the Create Issue post-function

newIssueKey: Stores the issue key of the last issue created by a Create Issue(s) post-function in the sequence. You can access it as:

newIssueKeys: Stores an array of the keys of all the issues created by any Create Issue(s) post-function in the sequence. You can access the created issues from

For example: to add a comment on the current issue with the keys of the issue created

You can access the information of a specific issue using the issue filter. For example: To get the assignee of the issue created by the Create issue post-function: