# Automatic Ticket Categorization and Assignment with Rovo in Jira & JSM > How Rovo AI automatically categorizes support tickets in Jira and routes them to the right team: the automation rule, the workflow, and the benefits for your support team. Source: https://www.xalt.de/en/blog/automatic-ticket-categorization-and-assignment/ TEAM XALT Atlassian Platinum Partner · 7 November 2024 · 6 min [Rovo Setup with XALT](https://rovo.xalt.de) The pressure on support teams is high: tickets must be processed quickly and correctly, categorised consistently, and assigned efficiently. However, manual sorting and assignment can be time-consuming and prone to errors – especially when ticket volume is high. This is where intelligent automation with Rovo AI in Jira comes into play: the automatic categorisation and assignment of tickets not only saves time but also increases the accuracy and response speed of your team. ## What is Rovo AI from Atlassian? [Rovo AI](https://www.atlassian.com/software/rovo) is Atlassian's AI-powered assistant, designed to make everyday work easier through intelligent automation. Rovo takes on numerous routine tasks and optimises processes in Atlassian tools such as Jira and Confluence. From the automatic categorisation and prioritisation of support tickets to the creation and management of documentation – Rovo analyses content, creates summaries, recommends next steps, and supports task management. Rovo AI is particularly useful for IT and service teams, as it processes requests in real time and ensures that the right information reaches the right people quickly. At the same time, Rovo improves collaboration and consistency in projects by independently handling frequent tasks and relieving teams. With Rovo AI, companies can increase their productivity, improve response times, and focus on more strategic tasks. ## Overload and inefficiency in support teams Support teams are often confronted with a flood of tickets that need to be processed in a timely manner. Manual categorisation and assignment often lead to: - **Team overload:** Due to repetitive tasks such as sorting tickets. - **Lack of consistency and accuracy:** Different people interpret ticket content differently, leading to unclear categories and delays. - **Slow response times:** Manually routing tickets costs valuable time. - **Inefficient resource utilisation:** Specialists spend time on tasks that could be automated. The solution? Rovo AI and Jira, which handle the automatic categorisation and assignment of tickets. ## Automatic categorisation and assignment in Jira with Rovo AI With Rovo AI, you can set up an automation that analyses tickets based on their description and subject and assigns them to a category – such as ITSM or HR. The ticket is then automatically forwarded to the responsible person or department. Here is a step-by-step guide on how to set up the automation: ### 1. Automation rule: Ticket creation as trigger The automation starts as soon as a new ticket is created in [Jira](https://www.xalt.de/en/atlassian-jira/)/ [Jira Service Management](https://www.xalt.de/en/jira-service-management/). The rule “When: Issue created” is set as the trigger to ensure that Rovo can intervene immediately as soon as a new ticket comes in. ![Automatische Kategorisierung und Zuweisung von Tickets - Workflow in Jira/JSM zur Automatisierung](https://cdn.sanity.io/images/c475o02b/production/35e1c6ed953ccc1eb5e659956aebddfdc1055a21-2103x1191.png?w=1504&q=75&fit=max&auto=format) ### 2. Categorisation by Rovo AI Rovo AI takes over the analysis of the ticket description and checks whether the ticket belongs to the ITSM (IT Service Management) or HR category. This is done through a query to the Rovo agent integrated into the automation. ![Screenshot einer Jira-Automatisierungsregel mit dem Schritt „Use Rovo Agent": rechts die Auswahl des Agenten Service Request Helper und das Prompt-Feld mit der Anweisung zur Kategorisierung](https://cdn.sanity.io/images/c475o02b/production/a5c7a1d81e36a725abdcb794b7fc6b9cc47ad718-1569x580.png?w=1504&q=75&fit=max&auto=format) ### 3. Adjusting ticket fields Based on the Rovo analysis, the ticket’s “Description” field is supplemented with the categorisation finding, so that all relevant information is summarised in the ticket. ![Screenshot einer Jira-Automatisierungsregel: links die Schritte von „Issue created" über „Use Rovo Agent" zu „Edit issue fields", rechts die Konfiguration des Beschreibungsfelds mit der Variablen agentResponse](https://cdn.sanity.io/images/c475o02b/production/55fd2411fa608005e71d3b097b58d5f57d42d1c5-1576x552.png?w=1504&q=75&fit=max&auto=format) ### 4. Conditional forwarding to the appropriate department If the ticket belongs to the “ITSM” category, it is automatically assigned to an ITSM specialist. However, if it is an HR ticket, a corresponding message is added and the ticket is forwarded to the HR team. This logic ensures that the ticket always goes to the right person or department. ![Kategorisierung von Issues: Automatische Kategorisierung und Zuweisung von Tickets mit Rovo in Jira & JSM](https://cdn.sanity.io/images/c475o02b/production/88c2f082ac1db6cb8a0b0dc87f5554ee6c34b3e3-1920x1080.jpg?w=1504&q=75&fit=max&auto=format) ### 5. Automatic email notification As soon as the ticket has been assigned to a category and forwarded, the ticket creator automatically receives a confirmation by email. This notification informs them about the receipt and further processing of the ticket. ![Screenshot einer Jira-Automatisierung mit der Aktion „Send email": Empfänger, Betreff mit Vorgangsschlüssel und ein vorformulierter Nachrichtentext](https://cdn.sanity.io/images/c475o02b/production/ecb2cfcb4393ff49527152b1d2d5bb475ab1dc67-1920x1080.jpg?w=1504&q=75&fit=max&auto=format) ### 6. Adjust ticket status To conclude, the ticket status is set to 'In Progress', which informs the team of the current processing status and makes progress transparent. ![Screenshot einer Jira-Automatisierung: die Aktion „Transition issue" mit dem Zielstatus „IN PROGRESS" im Auswahlfeld](https://cdn.sanity.io/images/c475o02b/production/0d69bca16377ec32454a2ccb2357f677bb8b983f-1920x1080.jpg?w=1504&q=75&fit=max&auto=format) ## Automatic categorisation and assignment of tickets in Jira - The benefits This automation brings significant benefits to your support team: - **Reduced team overload:** Routine tasks are automated, allowing the team to focus on more important tasks. - **Consistency and accuracy:** Automatic categorisation eliminates interpretation errors and ensures uniform assignment. - **Faster response times:** Tickets are categorised and forwarded immediately, reducing processing time. - **More efficient resource utilisation:** Specialists can focus on more complex tasks while Rovo AI handles the routine work. With Rovo AI and Jira, you bring a new level of efficiency to your support team. Automatic categorisation and assignment of tickets save time, reduce errors, and increase the satisfaction of your team as well as ticket creators. This solution is not only fast and effective but also easy to implement. Try it out and relieve your team of routine tasks so you can focus on the truly important challenges! ## Ready to categorize tickets automatically? We help you set up Rovo AI in Jira and Jira Service Management so tickets land in the right place instantly. [Talk to us](https://www.xalt.de/en/contact/) ## More articles ### [Personal AI Agents Compared: Rovo, OpenClaw, and Agent SDKs Like Claude or OpenAI](https://www.xalt.de/en/blog/personal-ai-agents-compared-rovo-openclaw-and-agent-sdks/) Rovo, OpenClaw, or Claude/OpenAI: how personal AI agents differ in 2026 and which approach fits your team. *Atlassian* ### [BaFin Compliance for Atlassian Cloud – What Financial Institutions Need to Know Now](https://www.xalt.de/en/blog/bafin-compliance-atlassian-cloud-migration/) New EU FSA rules have been in effect for Atlassian Cloud in financial services since December 2024. We show what has changed and how you can migrate to the cloud in a BaFin-compliant way. *Atlassian* ### [Atlassian Team '26 Recap: The Shift to the AI-Native Organization and the Role of the Teamwork Graph](https://www.xalt.de/en/blog/atlassian-team-26-recap-teamwork-graph/) XALT was on the ground at Atlassian Team '26 in Anaheim. Our recap covers the Teamwork Graph, Rovo, and the new Teamwork, Service, Product, Software, and Strategy Collections – and what it means for enterprises in Germany. *Atlassian* --- *This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*