As the name suggests, post functions are functions that occur after (post) a transition has been executed. This allows you to perform additional processes once you have executed a transition. Jira makes heavy uses of post functions internally to perform a lot of its functions. For example, when you transition an issue, Jira uses post functions to update its search indexes so your search results will reflect the change in issue status.
If a transition has failed to execute (for example, failing validation from validators), post functions attached to the transition will not be triggered. The following table shows a list of post functions that come shipped with Jira, and additional post functions can be added via third-party add-ons:
|
Post function |
Description |
|
Assign to Current User |
This assigns the issue to the current user if the current user has the assignable user permission. |
|
Assign to Lead Developer |
This assigns the issue to the project/component lead developer. |
|
Assign to Reporter |
This assigns the issue to the reporter. |
|
Create Perforce Job Function |
This creates a perforce job (if required) after completing the workflow transition. |
|
Notify HipChat |
This sends a notification to one or more HipChat rooms. |
|
Trigger a Webhook |
If this post function is executed, Jira will post the issue content in JSON format to the URL specified. |
|
Update Issue Field |
This updates a system field such as Summary to a given value. |