These types vary in complexity, but overall, you can configure a set of useful rules without any prior knowledge. Depending on your needs, you can combine different types of automation.<\/p>\n\n\n\n
Whatever mix you choose, the impact is similar: faster ticket processing, less manual work for agents, and more consistent processes across your service desk.<\/p>\n\n\n\n
When to Use Automation in JSM<\/h2>\n\n\n\n
Here are some of the common use cases:<\/p>\n\n\n\n
- \n
- Repetitive actions:<\/strong> Creating and assigning tickets, sending notifications<\/li>\n\n\n\n
- Standard processes:<\/strong> Onboarding, approvals, escalations<\/li>\n\n\n\n
- Dependencies and SLAs:<\/strong> Setting breach alerts and progress reminders<\/li>\n\n\n\n
- Ticket hygiene: <\/strong>Auto-closing stale requests, re-opening after a customer comments<\/li>\n\n\n\n
- Workflow automation:<\/strong> Transferring tickets to a new status automatically<\/li>\n\n\n\n
- Managing forms:<\/strong> Passing tickets to the assignee after the customer submits a form<\/li>\n<\/ul>\n\n\n\n
How Jira Automation Works<\/h2>\n\n\n\n
In practice, JSM automation runs as a background \u201cobserver\u201d for your projects. It listens for events in the system, checks which rules apply to them, and then carries out the configured updates to your tickets.<\/p>\n\n\n\n
Automation rules are built from several key components:<\/p>\n\n\n\n
- \n
- Trigger:<\/strong> When a trigger event happens, the automation rule runs. For example, \u201cWork item created\u201d or \u201cComment added.\u201d<\/li>\n\n\n\n
- Condition:<\/strong> Once the rule runs, it checks whether the conditions specified in the rule are met. If yes, the prescribed action is performed.<\/li>\n\n\n\n
- Branch:<\/strong> This element lets you set separate conditions for a subgroup of work items (e.g., subtasks).<\/li>\n\n\n\n
- Action:<\/strong> Defines what the automation does when the rule is triggered and all conditions are met.<\/li>\n<\/ul>\n\n\n\n
In addition to regular Jira Automation triggers, JSM includes service-specific ones. For example, it can be \u201cService limit breached,\u201d \u201cSLA threshold breached,\u201d \u201cForm attached,\u201d or \u201cForm submitted.\u201d <\/p>\n\n\n\n
![\"\"](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/1-2.png\")
<\/figure>\n\n\n\n<\/p>\n\n\n\n
As an example of Jira Service Management automation, let\u2019s take a look at this rule for ITSM. It checks the request type of each new ticket and adds an approver if this field value is not specified yet:
<\/p>\n\n\n\n![\"Jira](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/2-1024x629.png\")
<\/figure>\n\n\n\nHere, we can see such elements:<\/p>\n\n\n\n
- \n
- Trigger – Work item created<\/li>\n\n\n\n
- Condition 1 – Request type is one of the specified options<\/li>\n\n\n\n
- Condition 2 – The Approvers field is empty<\/li>\n\n\n\n
- Action – Edit the Approvers filed \/ add approvers to the ticket<\/li>\n<\/ul>\n\n\n\n
This eliminates the need to manually sort tickets and add approvers, saving you time and effort.<\/p>\n\n\n\n
How to set up a Jira automation rule?<\/h2>\n\n\n\n
Please note that you must have Administrator permissions for your project\/space to be able to create Jira Service Management automation rules.<\/p>\n\n\n\n
- \n
- Navigate to your JSM space in the Jira menu on the left. Click the three dots -> Space Settings (Project Settings) -> Automation -> Create Rule -> Create From Scratch (see the screenshot below). <\/li>\n\n\n\n
- Select the trigger. Type in the action or event you\u2019d like to add as a trigger into the search bar and find it on the list. For example, Work item created (Issue created) or Work item commented.<\/li>\n\n\n\n
- Add conditions to your rule and specify the required details (optional). For example, Request Type is Procurement, or the Reporter field is empty.<\/li>\n\n\n\n
- Select the action that should be performed and provide the details related to that action.<\/li>\n\n\n\n
- Save and turn on your rule. You can also validate it before enabling it.<\/li>\n<\/ol>\n\n\n\n
![\"Jira](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/3.png\")
<\/figure>\n\n\n\nPractical Examples of Jira Service Management Automation<\/h2>\n\n\n\n
1. Auto-Assign JSM Tickets Based on Request Type<\/h3>\n\n\n\n
Typically, organizations have dozens of request types to categorize user submissions. It\u2019s recommended to set up a rule that checks the request type and automatically assigns the ticket to the responsible person. So, instead of agents checking each new ticket and deciding who should pick it up, the system will route it to the right person from the start. This reduces manual triage and helps you respond more quickly to new requests.<\/p>\n\n\n\n
Here\u2019s an example of such a rule for HR tickets. When a new ticket with the request type Recruitment launch is created, it is automatically assigned to the recruiter responsible for hiring:<\/p>\n\n\n\n
![\"1.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/4-1024x774.png\")
<\/figure>\n\n\n\nIn general, auto-assigning tickets is a typical use case for Jira Service Management automation. Depending on your needs, you can add more conditions or select other triggers – for instance, assigning based on keywords in the ticket description. <\/p>\n\n\n\n
This allows you to handle more complex scenarios and ensure that tickets don\u2019t wait too long without an owner.<\/p>\n\n\n\n
2. Create Clones of JSM Tickets in Another Project in Jira<\/h3>\n\n\n\n
In many teams, the service desk is just the front door, while the actual work on requests happens in a separate Jira project. For example, a software user raises a ticket requesting a new feature. While the request itself needs to be tracked and handled in JSM, the dev team will need to include this task in their Jira scope. <\/p>\n\n\n\n
You can add a rule that automatically clones the service request into the delivery project once its status moves from To Do to In Progress. This way, agents keep tracking the original ticket in JSM, and the dev team gets a regular Jira work item with the same summary, description, and key fields. Additionally, such tickets can be linked, so the service team can easily track the progress of the delivery ticket.<\/p>\n\n\n\n
![\"2.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/unnamed-11-1024x694.png\")
<\/figure>\n\n\n\nIf you need more control, add conditions to the rule so it only runs for certain request types or for summaries that contain specific keywords. <\/p>\n\n\n\n
3. Auto-add Checklists to JSM Tickets Based on Request Type<\/h3>\n\n\n\n
Another useful case for Jira Service Management automation is adding checklists. In this example, we\u2019ll show you how to set up a rule that automatically adds a Smart Checklist to tickets of a specific request type. <\/p>\n\n\n\n
For instance, when an employee submits a ticket with the request type Business Trip, the rule adds a ready-made business trip planning checklist to that ticket. The assignee receives a processing-ready request with a clear list of steps to follow. <\/p>\n\n\n\n
As a result, your team doesn\u2019t have to start from scratch every time. This will save you time and ensure consistent handling of repetitive requests.<\/p>\n\n\n\n
![\"3.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/5-1024x629.png\")
<\/figure>\n\n\n\nTo use checklists in your Jira work items, you first need to install Smart Checklist<\/strong><\/a> by Titan Apps and create a template. After this, start setting up your rule and select Import Checklist Template as an action. Then, click Connect and provide the Template ID<\/a>. <\/p>\n\n\n\n
Once you enable your rule, it will automatically add the selected checklist to your JSM tickets according to the selected parameters:<\/p>\n\n\n\n
![\"3.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/6-850x1024.png\")
<\/figure>\n\n\n\nAdditionally, you can choose to Show Smart Checklists on the Customer Portal<\/a>. In this case, your customer (or other stakeholders) can view the checklist and see the progress on their request. The checklist will be shown in the view-only mode, so the customer won\u2019t be able to change it.<\/p>\n\n\n\n
Obviously, the same logic applies not only to Business Trip requests but also to many other use cases. <\/p>\n\n\n\n
Checklist templates you can use with JSM automation:<\/strong><\/p>\n\n\n\n
- \n
- Business Travel Template<\/a><\/li>\n\n\n\n
- Hardware Procurement Template<\/a><\/li>\n\n\n\n
- Procurement Checklist Template<\/a><\/li>\n\n\n\n
- Payroll Template for Jira<\/a><\/li>\n\n\n\n
- Invoice Approval Template<\/a><\/li>\n\n\n\n
- Ticket Triage and Prioritization Checklist<\/a><\/li>\n\n\n\n
- Vendor Due Diligence Checklist<\/a><\/li>\n<\/ul>\n\n\n\n
\n \nAdd checklists to your Jira tasks<\/h5>\n
- View a progress bar<\/li>\n <\/ul> Try it free<\/a>\n <\/div>\n \n
![\"\"](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/10\/Ui-for-promo-banner.svg\")
\n <\/div>\n<\/section>\n\n\n\n<\/p>\n\n\n\n
4. Re-open a JSM Ticket When a Customer Adds a Comment<\/h3>\n\n\n\n
Sometimes, customers reply to tickets that agents have already marked as resolved. To more easily track those updates, you can set up an automation rule: when a customer adds a comment, the ticket is moved from Done back to In Progress. <\/p>\n\n\n\n
Here\u2019s what the rule looks like. It\u2019s triggered when a comment is added to a JSM ticket; it then checks whether the ticket\u2019s status is Done and whether the initiator is a customer. If yes, the ticket is transitioned to an active status:<\/p>\n\n\n\n
![\"4.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/7-1024x774.png\")
<\/figure>\n\n\n\nThis way, follow-up questions and extra details won\u2019t be missed and can be addressed in time.<\/p>\n\n\n\n
You can use this example to also set up other rules that change a ticket\u2019s status based on the last added comment. For open tickets, if a customer comments providing you with new information, the ticket can be automatically moved to Waiting for Review. If your agent adds a comment, the status can change to Waiting for Customer. <\/p>\n\n\n\n
This Jira Service Management automation can save you significant time on repetitive tasks, especially if your team handles many tickets daily. It also helps you maintain consistency and minimize the probability of human errors. <\/p>\n\n\n\n
5. Auto-Close Tickets if the Customer Doesn\u2019t Respond<\/h3>\n\n\n\n
Sometimes, tickets stay in the Waiting for Customer status for days because no one has time to follow up. This makes queues look busy even when many requests are no longer active. To clean this up, you can add a rule that closes tickets after a period of inactivity and leaves a final comment for the customer.<\/p>\n\n\n\n
In this example, the rule checks for tickets that have been waiting for a customer reply for 5 days. If there are no new comments from the customer during that time, the ticket is moved to Done. Also, the rule auto-adds a comment explaining that the request is being closed for now. The message tells the customer that they can come back and reopen the request if they still need help.<\/p>\n\n\n\n
![\"5.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/8-1024x774.png\")
<\/figure>\n\n\n\nThis rule can be reused with different time frames for different queues or priorities. High-priority incidents can stay open longer, while simple questions can close sooner. If needed, you can also add an extra step to notify the customer in advance before closing the ticket.<\/p>\n\n\n\n
Combined with the \u201cre-open on comment\u201d rule from the previous example, this Jira Service Management automation creates a clear loop. Tickets close automatically when there\u2019s no response and instantly return to an active status if the customer replies again.<\/p>\n\n\n\n
6. Auto-create work items from Smart Templates<\/h3>\n\n\n\n
Some JSM tickets require a standard set of tasks in another Jira project. For instance, an HR team receives a hiring request via the self-service JSM helpdesk, but it needs to create a batch of tasks in a regular Jira Cloud instance to work on that request.<\/p>\n\n\n\n
As recruitment is a recurring process, it makes sense to reuse the same set of pre-configured work items rather than create them from scratch every time. This can be done using Smart Templates for Jira<\/a> alongside native Jira Service Management automation. <\/p>\n\n\n\n
Smart Templates allow you to save any set of work items as a reusable template. Then, Jira automation can trigger the generation of tasks from that template based on your conditions.<\/p>\n\n\n\n
Here\u2019s an example of a template for recruitment. It consists of a task with several subtasks and checklists. It also contains variables for dynamic values, such as {{position}} and {{project}}. This allows you to easily adjust one template for multiple uses.<\/p>\n\n\n\n
![\"6.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/unnamed-12-1022x1024.png\")
<\/figure>\n\n\n\nFirst, you will need to prepare your template in the Jira project where you need to generate new fork items from that template. <\/p>\n\n\n\n
Once done, you can configure the automation rule. When a new ticket with the \u201cRecruitment launch\u201d request type is created, the automation will generate the set of tasks from your template:<\/p>\n\n\n\n
![\"6.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/9-1024x629.png\")
<\/figure>\n\n\n\nFor more details on configuring this rule, please see our knowledge base on Confluence: Using Smart Templates with Automation<\/a>.<\/p>\n\n\n\n
- Hardware Procurement Template<\/a><\/li>\n\n\n\n
- Business Travel Template<\/a><\/li>\n\n\n\n
- Condition:<\/strong> Once the rule runs, it checks whether the conditions specified in the rule are met. If yes, the prescribed action is performed.<\/li>\n\n\n\n
- Standard processes:<\/strong> Onboarding, approvals, escalations<\/li>\n\n\n\n
![\"\"](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/11\/Smart-Templates_Jira___.svg\")
\n <\/div>\n<\/section>\n\n\n\n![\"7.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/10-1024x629.png\")
<\/figure>\n\n\n\n![\"8.](\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/12\/11-1024x774.png\")
<\/figure>\n\n\n\n
<\/div>\n\n