# Bug reports, alerts and dev questions, handled in Slack and Teams

Risotto keeps internal requests out of your sprint. It answers the setup and policy questions your docs already cover, with the source cited. A real bug becomes a ticket that syncs with Linear or Jira, so the person who reported it hears back in their thread when it's fixed. And staging access arrives once the right person approves it, without anyone on your team touching Okta.

[Book a demo](/demo) · [For developers](/developers)

**86%** auto-solve rate in Engineering at Thinkific. [Read the story](/customers/thinkific-automates-46-percent-support-tickets-with-risotto)

## Bug reports that reach your tracker, and report back

Risotto turns a bug report in Slack or Teams into a ticket in your engineering department, and that department's tickets sync both ways with Linear, in the team and with the labels you choose. When an engineer comments on the issue, the comment shows up in the reporter's thread under the engineer's name. When the issue is done, the ticket resolves. Prefer Jira? It syncs both ways too. GitHub issues are created one-way.

[Risotto and Linear](/integrations/linear) · [Risotto and Jira](/integrations/jira)

Nina's bug report syncs to Linear as WEB-2048. Tom's comment on the issue reaches her thread, and the ticket resolves when the issue is done. Example data.

## Every alert gets an owner

Turn on "Ticket everything" in your alerts channel and add your monitoring bots to its allowlist, and each alert they post becomes a Risotto ticket. Risotto hands it straight to your team's channel and tags your escalation contact, and routing rules assign it: round robin, fewest open tickets, or whoever is online in Slack. Want a page instead? Start from the on-call templates in the library.

[Ticketing](/product/ticketing)

Datadog posts a latency alert at 2:07 AM; Risotto opens ENG-311 and tags Tom in the on-call channel. Example data.

## Answers from your docs, so nobody has to repeat them

Risotto answers setup, tooling and policy questions from your engineering docs in Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda, and cites the page it used. Resolved threads become knowledge too, so a question answered in your help channel once gets answered by Risotto the next time.

[Knowledge](/product/knowledge)

Marcus asks about adding an npm package, and Risotto answers from the dependency policy with the source cited. Example data.

## Ask about a ticket from Claude, Cursor or any MCP client

Engineers already live in Claude Code and Cursor. Risotto's MCP server lets them read a ticket, see why Risotto did what it did, and reply, without opening the dashboard, with the same permissions they have in Risotto. Admins can do more, such as building runbooks, and every change still waits for approval.

[MCP server and API](/product/mcp)

In Claude, someone asks why Risotto closed a ticket, and Claude answers from the ticket's own record. Example data.

## Built for engineers to build on

Risotto gives your engineers the same building blocks it uses.

- **TypeScript script tools.** Write steps that must run the same way every time, test them in Script Studio, and read every run.
- **A public API.** Open and update tickets from your own services, with scoped keys.
- **Signed webhooks.** Get ticket events in your own systems, signed so you can verify them.
- **Your own tools.** Build a tool from any vendor's API spec or docs, or connect your own MCP servers.
- **Production access, approved.** Engineers ask for production access, Security approves it, and Risotto removes it on time.
- **Secrets kept out of code.** API keys live in Risotto's credential vault and go only to the hosts you approve.

[For developers](/developers) · [Security teams](/solutions/security)

## Start from the library

Start from one of these and change it to fit. Open one to see every step and tool, or [browse the library](/library).

### Every alert gets an owner

On-call gets the ticket, with the context.

- [Escalated ticket on-call alert](/library/automations/escalated-ticket-oncall-alert): post the ticket to on-call, with the requester's manager
- [On-call escalation](/library/script-tools/oncall-escalation): page on-call through PagerDuty, with the requester's manager
- [Service health sweep](/library/script-tools/service-health-sweep): one incident ticket for every vendor that's down

### Dev tool access

Access without a trip to Okta.

- [Jira project access](/library/runbooks/jira-project-access): add the person to the Jira project they need
- [Okta group access request](/library/runbooks/okta-group-access-request): check your access rules, get the approval, add the person to the group

## Frequently asked questions

### Does Risotto sync with Linear?

Yes. A department's Risotto tickets sync both ways with Linear, in the team and with the labels you choose. Linear comments reach the requester's thread under the commenter's name, and a done issue resolves the ticket. [Risotto and Linear](/integrations/linear)

### Can Risotto file issues in GitHub or Jira?

Yes. Jira Cloud and Jira Service Management sync both ways. GitHub issues are created one-way: Risotto creates the issue and posts ticket replies to it, and changes in GitHub don't sync back. [Risotto and Jira](/integrations/jira)

### Can Risotto turn monitoring alerts into tickets?

Yes. In a Slack channel with "Ticket everything" on, posts from the bots on its allowlist become tickets, and Risotto hands each one to your team's channel for an owner. [Ticketing](/product/ticketing)

### Can Risotto answer engineering questions from our docs?

Yes. Risotto answers from Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda with the source cited, and from your help channel's resolved threads. [Knowledge](/product/knowledge)

### Can engineers use Risotto from Claude Code or Cursor?

Yes. Risotto's MCP server works with Claude and any MCP client, with the same permissions each person has in Risotto. [MCP server and API](/product/mcp)

## Turn Slack requests into action items instead of engineering interruptions

[Book a demo](/demo)

Source: https://www.tryrisotto.com/solutions/engineering
