# Jira Service Desk AI employee Viktor works in Jira Service Desk for you. Ask in Slack or Microsoft Teams. Viktor is an AI employee that connects to Jira Service Desk and helps you triage and resolve customer support tickets, running 19 Jira Service Desk actions for you like Find Users, List Sites, and Get Request. Ask in plain English from your workspace; Viktor does the work in Jira Service Desk and reports back. Viktor connects in one click via OAuth. - Tool: Jira Service Desk - Category: Productivity - Connection: One-click OAuth - Actions available: 19 - Currently available in: Slack, Microsoft Teams, and Discord - Page: https://viktor.com/integrations/jira-service-desk ## What can your AI employee do in Jira Service Desk? Viktor connects to your Jira Service Desk account and completes work in it. He doesn't just answer questions about Jira Service Desk, he takes the actions on your behalf and delivers the finished result to your workspace. 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 9,800+ tools he connects to, and asks for approval before anything sensitive runs. ### About Jira Service Desk Work with Jira Service Desk-specific entities, such as requests. ### How a run works 1. **You ask in your workspace** - Describe what you need in plain English 2. **Viktor picks the actions** - Selects from 19 Jira Service Desk actions, chains them together 3. **Runs in Jira Service Desk** - Helps you triage and resolve customer support tickets - your real data. 4. **Reports back** - Delivers the finished result to your workspace ## Use Jira Service Desk from Slack and Microsoft Teams Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Jira Service Desk, does the work and posts the result in the same thread, so nobody has to switch tabs. He can also run Jira Service Desk work on a schedule, like a weekly Jira Service Desk summary posted to your team's channel. Anything sensitive waits for your approval before it runs. ## 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. - Viktor is not affiliated with or endorsed by 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 flag them for me." ## How does Viktor work with Jira Service Desk? 1. Open Viktor in a supported workspace. 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 can Viktor do in Jira Service Desk? (19 actions) - **Create Comment on Request** - Create a comment on a customer request. - **Create Request** - Creates a customer request (ticket) in a Jira Service Management service desk. - **Download Issue Attachment** - Download the binary content of a Jira Service Desk attachment to the file-stash directory, returning the saved path plus the attachment metadata (filename, mimeType, size). Run List Issue Attachments first to obtain the attachment id, then pass both it and the same issueIdOrKey here. - **Find Service Desk Customers** - Finds the customers of one service desk by name or email address and returns the accountId of each match. - **Find Users** - Finds any active user on an Atlassian site by name or email address and returns the accountId of each match. - **Get Current User** - Returns the authenticated user's accountid, displayname, and email from Atlassian. - **Get Request Status** - Returns the status history of a Jira Service Desk request: the current status plus previous states with timestamps. - **Get Request** - Fetches the full details of a Jira Service Desk request including its field values and comment thread in a single response. - **List Cloud ID Options** - Lists the Atlassian sites you can raise requests on, as {label, value} options, to discover the cloudId every other Jira Service Desk tool needs. Takes no input beyond the account. - **List Issue Attachments** - List metadata for every attachment on a Jira Service Desk request. issueIdOrKey accepts either a Jira issue key (e.g. IT-42) or a numeric Jira issue ID (e.g. 10001). Results are paginated automatically up to maxResults. Returns { attachments, truncated }, where each attachment includes id, filename, size (bytes), mimeType, and content (an opaque reference URL whose exact shape varies by account access level and is not directly fetchable through this connection's authentication), and truncated is true when more attachments remained unfetched. Use Download Issue Attachment with an attachment id and the same issueIdOrKey to fetch the binary content — do not call content directly. If this connection has customer-level access rather than agent access, only public attachments are returned; internal attachments exist but won't appear here. Returns { attachments: [], truncated: false } (no error) when the request exists but has no visible attachments. - **List My Requests** - Lists Jira Service Desk requests owned or participated in by the current user. - **List Request Transitions** - Lists the available workflow transitions for a Jira Service Desk request, returning each transition's id and name. - **List Request Type Fields** - Lists the fields a given request type accepts, so you can build the additionalFieldValues argument for Create Request in a single pass. - **List Request Types** - Lists the customer request types a service desk offers, with the id, name, and description of each. - **List Service Desks** - Lists every service desk on an Atlassian site, with the id and project details of each. - **List Sites** - Returns all Atlassian cloud sites accessible to the authenticated user. - **Manage Request Attachment** - Adds, replaces, or deletes a single attachment on a customer request (ticket) that already exists. - **Transition Request** - Transitions a Jira Service Desk request to a new workflow status. - **Update Issue Fields** - Updates fields on an existing Jira Service Desk request via the Jira platform API. ## 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) - [Salesforce](https://viktor.com/integrations/salesforce) - [Stripe](https://viktor.com/integrations/stripe) ## More Productivity integrations - [GitHub](https://viktor.com/integrations/github) - [Jira & Confluence](https://viktor.com/integrations/jira-confluence) - [Asana](https://viktor.com/integrations/asana) - [Monday.com](https://viktor.com/integrations/monday-com) - [Linear](https://viktor.com/integrations/linear) - [Notion](https://viktor.com/integrations/notion) - [Miro](https://viktor.com/integrations/miro) - [ServiceM8](https://viktor.com/integrations/servicem8) ## FAQ ### Does Viktor integrate with Jira Service Desk? Yes. Jira Service Desk is one of the 9,800+ tools Viktor connects to, in one click via OAuth. Once connected, anyone on your team can put Viktor to work in Jira Service Desk from their workspace - no workflow builder, no code. ### How do I connect Jira Service Desk to Viktor? Ask Viktor in your workspace 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 19 Jira Service Desk actions, including Find Users, List Sites, and Get 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 for Jira Service Desk? No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, 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; the Team plan is $100 a month. ### Can Viktor use Jira Service Desk together with my other tools? Yes - that's the point. Viktor connects to 9,800+ tools and works across them in a single run: he can pull data from Jira Service Desk, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in your workspace. ## Get started Viktor is free to start - up to $100 in credits, no credit card required. All 9,800+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.