# Jira Service Desk AI agent for Slack & Microsoft Teams Viktor is an AI employee that connects to Jira Service Desk in one click via OAuth and helps you triage and resolve customer support tickets, running 12 Jira Service Desk actions for you like List Sites, Get Request, and Create Request. Ask in plain English in Slack or Microsoft Teams; Viktor does the work in Jira Service Desk and reports back. Setup takes about two minutes. - Tool: Jira Service Desk - Category: Productivity - Connection: One-click OAuth - Actions available: 12 - Works from: Slack and Microsoft Teams - Page: https://viktor.com/integrations/jira-service-desk ## What can you ask Viktor to do in Jira Service Desk? - "Summarize today's open tickets in Jira Service Desk and flag the urgent ones." - "Draft replies to the open tickets in Jira Service Desk and queue them for my approval." - "Pull this week's ticket volume and response time from Jira Service Desk every Monday." - "Watch Jira Service Desk for tickets that mention churn and alert me immediately." ## What can Viktor do in Jira Service Desk? (12 actions) - **Update Issue Fields** - Updates fields on an existing Jira Service Desk request via the Jira platform API. Use this to change the summary, priority, description, or other fields after a request has been created. Use List Sites first to obtain the required cloudId. Use List My Requests or Get Request to find the issueKey (e.g. IT-42). fields is a JSON object of field name-value pairs. Example: {"summary": "Updated title", "priority": {"name": "High"}}. - **Transition Request** - Transitions a Jira Service Desk request to a new workflow status. Use List Request Transitions first to get valid transitionId values for the request. Use List Sites to obtain the required cloudId. Use List My Requests or Get Request to find the issueKey (e.g. IT-42). Optionally include a comment to explain the transition. - **List Sites** - Returns all Atlassian cloud sites accessible to the authenticated user. Call this tool first to obtain the cloudId (returned as id) required by every other Jira Service Desk tool. Each site includes its id (cloudId), name, and url. - **List Request Transitions** - Lists the available workflow transitions for a Jira Service Desk request — returns each transition's id and name. Call this before Transition Request to obtain valid transitionId values. Use List Sites first to obtain the required cloudId. Use List My Requests or Get Request to find the issueKey (e.g. IT-42). - **List My Requests** - Lists Jira Service Desk requests owned or participated in by the current user. Defaults to open requests owned by the current user. Use List Sites first to obtain the required cloudId. Each result includes issueKey, issueId, and request field values (summary, status). requestStatus: OPENREQUESTS (default), CLOSEDREQUESTS, or ALLREQUESTS. requestOwnership: OWNEDREQUESTS (default) or PARTICIPATEDREQUESTS. - **List Cloud ID Options** - Retrieves available options for the Cloud ID field. - **Get Request** - Fetches the full details of a Jira Service Desk request including its field values and complete comment thread in a single response. Use this to summarize a ticket without needing follow-up calls. Use List Sites first to obtain the required cloudId. Use List My Requests to find the issueKey of a request (e.g. IT-42). - **Get Request Status** - Returns the status history of a Jira Service Desk request — the current status plus all previous states with timestamps. Use this to understand how a request has progressed through the workflow. Use List Sites first to obtain the required cloudId. Use List My Requests to find the issueKey (e.g. IT-42). - **Get Current User** - Returns the authenticated user's accountid, displayname, and email from Atlassian. Use this to identify who is logged in, or to filter requests by the current user's accountid. No cloudId required — this uses the Atlassian Identity API directly. - **Create Request** - Creates a new customer request. - **Create Incident** - Creates a new incident request in a Jira Service Desk. Auto-discovers the best-matching request type (prefers types named 'incident' or 'problem') and, if serviceDeskId is omitted, auto-discovers it from the user's existing requests. Use List Sites first to obtain the required cloudId. serviceDeskId is optional — if not provided, the tool calls List My Requests to discover it automatically. Returns the new request including its issueKey and issueId. - **Create Comment on Request** - Create a comment on a customer request. ## How does Viktor work with Jira Service Desk? 1. Add Viktor to Slack or Microsoft Teams. 2. Connect Jira Service Desk with one-click OAuth - Viktor handles authentication. 3. Ask in plain English. Viktor runs the Jira Service Desk actions, chains them with your other tools when needed, and reports back. Sensitive actions wait for your approval. ## What is a Jira Service Desk AI agent? A Jira Service Desk AI agent is an AI that connects to your Jira Service Desk account and completes work in it - it doesn't just answer questions about Jira Service Desk, it takes the actions. Viktor is that agent: an AI employee that works in Jira Service Desk on your behalf and delivers the finished result in Slack or Microsoft Teams. Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Jira Service Desk actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs. ### About Jira Service Desk Work with Jira Service Desk-specific entities, such as requests. ## Security and permissions - One-click OAuth - Viktor never sees your password, and you can revoke access at any time. - Review-first approvals: sensitive Jira Service Desk actions wait for your sign-off before they run. - Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models. - SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ## FAQ ### Does Viktor integrate with Jira Service Desk? Yes. Jira Service Desk is one of the 3,200+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Jira Service Desk from Slack or Microsoft Teams - no workflow builder, no code. ### How do I connect Jira Service Desk to Viktor? Ask Viktor in Slack or Microsoft Teams to connect Jira Service Desk, then approve the one-click OAuth prompt. Viktor never sees your password, handles authentication itself, and starts working right away. Setup takes about two minutes, and you can revoke access at any time. ### What can Viktor do in Jira Service Desk? Viktor can run 12 Jira Service Desk actions, including List Sites, Get Request, and Create Request - and chain them with other tools in a single request. In practice that means Viktor helps you triage and resolve customer support tickets. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done. ### Do I need to build workflows to automate Jira Service Desk? No. Viktor isn't a workflow builder - there are no triggers to map and no workflows to maintain. You ask for the outcome in plain English in Slack or Microsoft Teams, and Viktor decides which Jira Service Desk actions to take, runs them, and reports back. ### Is my Jira Service Desk data secure with Viktor? Yes. Viktor connects to Jira Service Desk in one click via OAuth, runs in an isolated environment per team, and never trains models on your data. Sensitive actions wait for your approval, and you can revoke access at any time. Viktor is SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ### How much does the Jira Service Desk integration cost? Nothing extra - every integration, including Jira Service Desk, is available on every plan. You can start free with up to $100 in credits, no credit card required; paid plans start at $50/month. ### Can Viktor use Jira Service Desk together with my other tools? Yes - that's the point. Viktor connects to 3,200+ tools and works across them in a single run: it can pull data from Jira Service Desk, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in Slack or Microsoft Teams. ## Viktor uses Jira Service Desk together with - [Slack](https://viktor.com/integrations/slack) - [Gmail](https://viktor.com/integrations/gmail) - [Google Sheets](https://viktor.com/integrations/google-sheets) - [HubSpot](https://viktor.com/integrations/hubspot) - [Notion](https://viktor.com/integrations/notion) - [Salesforce](https://viktor.com/integrations/salesforce) ## More Productivity integrations - [GitHub](https://viktor.com/integrations/github) - [Asana](https://viktor.com/integrations/asana) - [Basecamp](https://viktor.com/integrations/basecamp) - [Monday.com](https://viktor.com/integrations/monday-com) - [Jira](https://viktor.com/integrations/jira) - [Linear](https://viktor.com/integrations/linear) - [Miro](https://viktor.com/integrations/miro) - [ServiceM8](https://viktor.com/integrations/servicem8) ## Get started Viktor is free to start - up to $100 in credits, no credit card required. All 3,200+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.