# Jira + Risotto: requests resolved in Slack and Teams, tickets kept in Jira

Risotto adds an AI agent to Jira Service Management. Employees ask in Slack or Microsoft Teams. Risotto resolves what it can and keeps every request as a Jira ticket, with comments, status, assignees and custom fields synced. Jira stays your system of record, and your agents keep working in Jira.

[Book a demo](/demo)

## Fewer tickets for your agents, one record in Jira

- **Tier 1 resolved in chat.** Password resets, software access and troubleshooting, done in Slack or Teams before an agent needs to look.
- **Two-way sync.** Every request becomes a Jira issue. Comments, status and assignees sync both ways, and replies from Jira reach the employee's thread.
- **Your fields, filled in.** Map Risotto's ticket fields to your Jira custom fields, so every issue arrives ready to report on.
- **One queue.** Issues created in a connected Jira project become Risotto tickets too.
- **Service catalog.** Your Jira Service Management request types, in chat. Risotto collects the answers and files the request.
- **Smarter with every issue.** Index a Jira project, and Risotto learns from past resolutions.
- **Jira access, granted.** Add people to Jira projects with a role, and add participants to a customer request.

## Live in three steps

1. **Install the Jira app.** Install Risotto's app for Jira Cloud and choose your projects.
2. **Map your setup.** Connect each department to a Jira project, match statuses and map fields. Sync every request, or only escalated ones.
3. **Employees ask.** In Slack, Teams or Jira. Your agents work in Jira, and Risotto keeps both sides current.

[Read the setup guide](/docs/integrations/ticketing/jira)

## Keep Jira for tickets. Add Risotto to resolve them.

**Jira keeps** your queues, workflows, SLAs, routing, reports and audit trail.

**Risotto adds:**

- Requests captured and resolved in Slack and Teams
- Answers from your knowledge base and past resolutions
- Routing to the right person when a ticket needs one
- Provisioning, resets and access requests end to end, with approvals and a log

When a request needs a person, Risotto's AI Assist investigates first and writes a plan your agent can approve. [See AI Assist](/product/ai-assist)

> "Risotto is one of the easiest tools I've implemented. We were up and running in less than a week and already seeing our first auto-solves." — Jason Huey, Senior IT Systems Administrator, ThoughtSpot

## Frequently asked questions

### Does Risotto replace Jira Service Management?

Only if you want it to. Risotto syncs both ways with Jira Service Management, so tickets stay where your team works. When you are ready to move, Risotto has its own ticketing. [Ticketing](/product/ticketing)

### What syncs between Risotto and Jira?

Risotto creates the Jira issue and syncs comments, status and assignees both ways. Custom fields go to the Jira fields you map, and updates from Jira reach the employee's Slack or Teams thread.

### Can Risotto use our Jira Service Management request types?

Yes. Risotto shows your request types in chat as a service catalog, collects the answers and files the request for the employee.

### How is Risotto different from Atlassian Rovo?

Risotto works in Slack and Teams, acts across your tools, such as Okta, Jamf and your HR system, and lets IT build automations by asking. Jira stays the system of record. [Risotto vs Jira Service Management](/compare/jira-service-management)

### How does Risotto connect to Jira?

Through Risotto's app for Jira Cloud, built on Atlassian Forge. Install it, pick your projects, and you are connected.

## See Risotto work your Jira queue from Slack and Teams

[Book a demo](/demo)

Source: https://www.tryrisotto.com/integrations/jira
