This section explains key concepts of the app such as workflow post functions, 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 is 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.
Create a change history record for the issue
Add a comment to an issue
Update an issue's field
Create 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 Create on Transition.
Validators check that any input made to the transition is valid before the transition is performed. Input can include information 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.
Conditions control whether the user can execute a transition. If a condition fails, the user won't be able to execute the transition. For example, the user won't see the transition button on the View issue page, and so will not be able to execute the transition.
Create Issue, Update Issue, and Create Subtask post functions support quite a number of fields (Issue fields) that can be configured to help you control:
Whenthe issue should be created and
What information is associated with the issue once created
Many of our customers have found it helpful to review each issue field and capability ahead of creating 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.