On this page
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.
All post functions, as opposed to conditions and validators, use the power of the expression parser to to get you the data you need, when you need it.
Available post functions
Jump right in and configure any of the available post functions listed below. Each post function comes with built-in examples.
If you need more help on how to construct expressions check out the documentation on the expression parser, and available field codes and operators or check out the use cases and examples below.
Get started in no time!
To help you getting started, JWT for Jira Cloud comes with a predefined set of example configurations that you can apply with a single click.
Use cases and examples
| Use case | JWT feature | Workflow function | Parser functions | Use case description | Complexity |
|---|---|---|---|---|---|
| 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. | BEGINNER | ||
| Transition parent issue to another status |
| Transition issue | filterByStatus() subtasks() | Transition the parent issue to the "Open" status. | BEGINNER |
| Automating annual access review for company software in assets |
| For the annual access review of applications used in the company and managed as Jira Service Management Assets, we want to create a dedicated task for each application owner to review the people who have access to the application they are responsible for. | INTERMEDIATE | ||
| Set the due date based on the priority |
| Update fields | getMatchingValue() | ||
| Set the Assignee based on the Issue type |
| Update fields | getMatchingValue() | ||
| Create a sub-task for each component |
| toStringList() getMatchingValue() | Create a sub-task for each selected component in the current issue. | BEGINNER | |
| 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. | INTERMEDIATE |
| 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 | BEGINNER | |
| 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. | BEGINNER | |
| 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. | BEGINNER | |
| 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. | BEGINNER | |
| 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. | BEGINNER | |
| Auto-transition when related issues are in a specific status |
| Transition issue | linkedIssues() | Automatically transition issue, if all linked issues are in specific status. | INTERMEDIATE |
| 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. | ADVANCED | |
| 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". | BEGINNER | |
| Providing information to the onboarding team about new issues created by team members |
| Add or remove watchers | Each time a team member creates a new issue, the "Add or remove watchers" functionality automatically adds all colleagues from the onboarding team as watchers. This feature immediately informs the entire onboarding team about new issues, improving team coordination and support. | ADVANCED | |
| Notify the support team about internally found bugs / problems |
| Add or remove watchers | When an issue is identified as a bug, the functionality automatically adds all members of the support group as watchers. This ensures the support team is promptly informed about the bug, enabling them to communicate effectively with customers regarding any errors that occur on the customer side. | INTERMEDIATE | |
| Notifying the parent issue watchers about new sub-tasks |
| Add or remove watchers | Once a sub-task is created, the functionality automatically adds all watchers of the parent issue as watchers to the sub-task. In this way, it becomes possible to ensure that the watchers of the parent issue remain informed of new developments and updates at the sub-task level and maintain a comprehensive overview. | BEGINNER | |
| Keep the project lead informed of any new issues |
| Add or remove watchers | Anytime a new issue is created in the "Project Management" Jira project, the functionality automatically adds the project lead as an observer. The project lead is thereby kept up to date with all new updates and information within the project, facilitating effective monitoring and management. | BEGINNER | |
| Keeping developers informed about new software requirements |
| Add or remove watchers | Each time a new software requirement was created in a Jira project, the functionality automatically adds all project developers as watchers. As a result, the development team is immediately informed of the new requirements, enabling better coordination and timely implementation. | BEGINNER | |
| Deleting watchers from rejected incidents |
| Add or remove watchers | After an incident is rejected, the functionality automatically removes all watchers from the issue. This guarantees that no other people remain in the information loop for the rejected issue, streamlining communication and focusing on active incidents. | BEGINNER | |
| 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. | BEGINNER | |
| 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. | BEGINNER | |
| 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). | BEGINNER | |
| 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. | BEGINNER | |
| Keep parent's priority in sync |
| Update fields | Set the priority of the parent issue to the priority of the current issue. | BEGINNER | |
| 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. | BEGINNER | |
| 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. | INTERMEDIATE | |
| 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" | BEGINNER | |
| 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. | INTERMEDIATE |
If you still have questions, feel free to refer to our support team.
