This section explains key concepts of the app such as workflow post functions, validators, issue fields, as well as when to use Original vs. Parent values.

Workflow Post Function

As a Jira administrator, one of the aspects of a workflow that you can control are post functions. The primary purpose of a post function is to carry out additional processing that may be required after a workflow transition has been executed. Examples include:

  • creating a change history record for the issue

  • adding a comment to an issue

  • updating an issue's field

  • creating an event to trigger one or more email notifications 

Jira has both essential and optional post functions and it is important that you understand their differences as they pertain to the introduction of new post functions with Update on Transition.


Validators check that any input made to the transition is valid before the transition is performed. Input can include that gathered from the user on the transition's screen. If a validator fails, the issue does not progress to the destination status of the transition, and the transition's post functions are not executed. 

Issue Fields

Update Issues post function supports quite a number of fields (Issue Fields) that can be configured to help you control both:

  • when the issue should be updated and

  • what information is associated with the issue once updated

Many of our customers have found it helpful to review each issue field and capability ahead of updating their first post function.

Original vs. Parent Values

Original Issue - The original issue that started the workflow transition. This could be an issue or sub-task.

Parent Issue - The parent issue of the original issue. If the original issue is not a sub-task, then parent is the same as original.