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||JWT feature||Workflow function||Parser functions||Use case description||Complexity|
|Create a sub-task for each component||toStringList() getMatchingValue()||Create a sub-task for each selected component in the current issue.|
|Add formatted comments automatically||Add comment|
Add a formatted comment to the current issue.
It would be convenient in case that you need to create a table or highlight some important points in the comment.
|Create a sub-task for each user selected in a User Picker field||Create automatically a sub-task for each selected user in a User Picker (multiple users) field of the transitioned issue.|
|Push status updates to the linked Epic||Add comment|
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).
|Add a comment with links to attachments that were just added||Add comment||A comment will be added to the current issue with links to the attachments included recently.|
|Add comment when rejecting an issue||Add comment||When an issue is rejected, a comment will be added to the current issue mentioning the reporter.|
|Transition parent issue to another status||Transition issue||Transition the parent issue to the "Open" status.|
|Start progress on the parent issue||Transition 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.
|Start progress on an issue immediately after creation||Transition issue|
The transition to start progress on the current issue will be executed directly after its creation.
|Fast-track transition issues assigned to the project lead||Transition issue||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||Transition issue|
When an issue is raised with a"Blocker" priority, a transition escalating the issue will be executed immediately after its creation.
|Auto-transition when related issues are in a specific status||Transition issue||linkedIssues()||Automatically transition issue, if all linked issues are in specific status.|
|Inform the project manager about an added attachment||Send email|
Within the Send email post function you have the possibility to send HTML links in the message as well.
|Alert the assignee of an important issue||Send email|
Send an email to the current assignee only if the priority is set to "Highest" or "High".
|Keep parent's priority in sync||Update fields||Set the priority of the parent issue to the priority of the current issue.|
|Assign important issues to the project lead||Update fields|
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.
|Create two sub-tasks when a user story is being approved||Create issue|
When a story is approved, two sub-tasks for Development and QA will be created.
|Create a sub-task mentioning the assignee when a high priority task is ready for review||Create issue|
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"
|Create a sub-task linked to issues with a specific priority||Create issue||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 issue|
Create a sub-task only if the priority of the current issue is "High".
|Create a story in an Epic||Create issue||Link your Epic each time you create a story.|
|Create a simple sub-task||Create issue|
Create a sub-task, set the summary based on the parent's component, and set the assignee to the current user.
|Create an issue with a summary to check for attachment type||Create issue||matches()|
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 an issue in the current project||Create issue|
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
|Push status updates to the parent||Add comment|
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).
|Alert the reporter||Add comment|
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 comment|
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