Post functions can be used to automate tasks and ensure consistent data quality by eliminating or at least minimizing human error.
Jira ships with built-in post functions but those are limited. JWT for Jira Cloud extends that list by offering custom post functions.
Available post functions
Jump right in and configure any of the available post functions listed below. Each post function comes with built-in examples.
Use cases and examples
|Use case||Function||Use case description||Complexity|
|Create an issue with a summary to check for attachment type|
Creating many issues and adding a summary and a description can be a bit frustrating and time-consuming.
To avoid such things, the following use case shows you how to create a sub-task with a summary to check for attachment type in the parent issue.
|Create a sub-task for each component||Create a sub-task for each selected component in the current issue, you can make use of this function to avoid repetitive tasks when you have multiple components and want to create a sub-task for each.|
|Add comment when rejecting an issue||When an issue is rejected, a comment will be added to the current issue mentioning the reporter.|
|Create a sub-task mentioning the assignee when a high priority task is ready for review|
Keep your team on track and up to date by creating a sub-task mentioning the assignee's full name and with issue links linked to the appropriate issue whenever a high priority issue has been moved to the status "Review"
|Keep parent's priority in sync||Set the priority of the parent issue to the priority of the current issue.|
|Push status updates to the linked Epic|
Add a comment to the linked Epic including the summary and status of the current issue.
This is helpful when you don't want to keep track of individual Stories and only receive notifications of the linked Epic (e.g. as a watcher or reporter).
|Push status updates to the parent|
Add a comment to the parent issue including the summary and status of the current issue.
This is helpful when you don't want to keep track of individual sub-tasks and only receive notifications of the parent issue (e.g. as a watcher or reporter).
|Start progress on an issue immediately after creation|
The transition to start progress on the current issue will be executed directly after its creation.
|Start progress on the parent issue|
When a sub-task is transitioned to the "In Progress" status the parent issue will be transitioned to the "In Progress" status as well if it is still in the "To Do" status.
|Transition parent issue to another status||Transition the parent issue to the "Open" status.|
|Fast-track transition issues assigned to the project lead||Automatically execute the "Start progress" transition if the issue's assignee is the project lead.|
|Escalate an issue if it is being raised with a "Blocker" priority|
When an issue is raised with a"Blocker" priority, a transition escalating the issue will be executed immediately after its creation.
|Create two sub-tasks when a user story is being approved|
When a story is approved, two sub-tasks for Development and QA will be created.
|Create a sub-task linked to issues with a specific priority||Create sub-tasks and link them to the parent or current issue that has a specific priority of your choice.|
|Create a sub-task for high priority issues|
Create a sub-task only if the priority of the current issue is "High".
|Create a story in an Epic||Link your Epic each time you create a story.|
|Create a simple sub-task|
Create a sub-task, set the summary based on the parent's component, and set the assignee to the current user.
|Create an issue in the current project|
Create an issue in the current project and additionally set a summary.
This use case comes in handy if you quickly need to create i.e. a new bug which relates to the current issue
|Auto-transition when related issues are in a specific status||Automatically transition issue, if all linked issues are in specific status.|
|Assign important issues to the project lead|
Automatically assign and issue to the project lead.
Issues will only be re-assigned if the priority of the issue is set to Highest to make sure that only important issues are being escalated.
|Alert the reporter|
Add a simple comment to an issue mentioning the reporter.
This use case might come in handy if you don't want to use extra events in your notification schemes to notify specific users - like the reporter.
|Alert the assignee of important issues|
Add a comment to an issue mentioning the assignee.
The comment will only be added, if the issue priority is set to "High" or "Highest" to ensure that the assignee will only be alerted for the important issue