Post functions are provided with an option to delay their execution. You need to select the number of seconds to wait until the post-function is run, a default of 1 sec to a maximum of 20 seconds.Image Removed
...
Workflows Workflows that depend on post functions being executed in a specific order fail due due to the asynchronous nature of the Connect post-functions in Jira Cloud. A workaround to this is, One of the workarounds is to delay the execution of the post-functions and thereby create 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 use case below.
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.
Expand |
---|
| panel |
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.
|
panelAdd 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.
Expand |
---|
|
Panel | from 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.
|
panelAdd 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.
|
|