# Set up Jira with Risotto (video)

A three-and-a-half-minute video of the ten steps to connect Jira, turn on ticket sync for a department, test it in Slack and Microsoft Teams, and make a Jira project a request source.

Watch the whole Jira setup in three and a half minutes. Jira stays your system of record. Requests from Slack and Microsoft Teams become Jira issues, and requests raised in Jira come into Risotto, all kept in sync, both ways. Each step below links to its written guide.

[Video: Set up Jira with Risotto](https://media.tryrisotto.com/videos/jira-setup-desktop.mp4)

Before you start, make sure you are an Org Admin in Risotto and an organization admin in Jira. See [Permissions](https://www.tryrisotto.com/docs/operating/permissions) and Atlassian's [Make someone an organization admin](https://support.atlassian.com/user-management/docs/give-users-admin-permissions/#Improved-user-management-experience).

## Connect Jira and link it to a department

1. **Connect Jira**

   In **Settings**, open **Integrations**, then **Jira**. On the **Jira app**
   card, click **Connect**. Enter your Jira site URL, like
   `northwind.atlassian.net`, and click **Get install link**. See
   [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira).

2. **Install the Risotto app on your Atlassian site**

   Click **Open install page**, then review and approve the permissions. You
   need to be an organization admin in Jira. Come back to Risotto: it detects
   the install on its own. Click **Done**, and Jira shows as **Connected**.
   See [Initial Jira Sync Setup](https://www.tryrisotto.com/docs/guides/initial/jira-sync).

3. **Choose who replies post as**

   This step is optional. In the **Replies post as** row, leave it as the
   Risotto app, or enter the email of a dedicated Jira user, like a shared
   support account, and click **Save**. See [Post agent replies as your own
   Jira
   user](https://www.tryrisotto.com/docs/integrations/ticketing/jira#post-agent-replies-as-your-own-jira-user).

4. **Link Jira to a department**

   Go to **Settings > Departments > IT > Ticket Sync**. Click **Add ticket
   sync**, and choose **Jira**. See [Ticket
   sync](https://www.tryrisotto.com/docs/dashboard/settings/departments#ticket-sync).

5. **Configure the project**

   Pick the Jira project for IT, then the issue type. For a Jira Service
   Management project, pick the request type too. Under **Status Mapping**,
   map each Risotto status to a Jira status, at least **Resolved**,
   **Closed**, and **Waiting for support**. Statuses you don't map won't
   sync. Turn on **Sync priority to Jira** if you want priorities to match,
   then click **Save**. See [Jira status
   sync](https://www.tryrisotto.com/docs/integrations/ticketing/jira-status-sync).

## Requests from Slack and Teams

1. **Choose when tickets sync**

   On the **Ticket Sync** page, **External ticket sync enabled** is on. Leave
   **Only sync escalated tickets** off to create a Jira issue for every
   request, or turn it on to sync only the requests your team needs to
   handle. **Show external ticket ID** puts the Jira key in the Slack thread.

2. **Test it in Slack**

   Post a request in your help channel. Risotto creates ticket IT-1 and syncs
   it to Jira. Open the issue: the summary and description come from the
   request, the employee is the reporter when their email matches a Jira
   user, and there's a link back to the ticket in Risotto. Add a public
   comment in Jira, and it shows up in the employee's Slack thread. Their
   replies come back as comments. Move the issue to the status you mapped to
   Resolved, and the Risotto ticket resolves too.

   Microsoft Teams works the same way, with the same department settings. In Teams, employees see the ticket number, but not the Jira key.

## Requests raised in Jira

1. **Make Jira a request source**

   In **Settings**, open **Request Sources**. On the **Jira** card, click
   **Manage in Jira**. On the **Requests** tab, click **Add Project**, pick the
   IT department, and click **Create**. The dialog asks only for the
   department: the project is the one IT already syncs to. See [Setting up Jira
   as a request source](https://www.tryrisotto.com/docs/operating/creating-tickets-jira).

2. **Choose what comes in**

   Expand the project. Issue types follow the department settings, so this
   project takes Service Requests: the row shows the type with a lock. You can
   also limit request types, or leave them as they are to take every request
   type.

3. **Test it from your portal**

   Raise a request in your Jira portal. It shows up under **Tickets** in
   Risotto, linked to the Jira issue. Risotto's reply posts as a comment, so
   the employee sees it in the portal. And your team keeps working in Jira,
   because comments sync both ways.

Next, connect your [knowledge](https://www.tryrisotto.com/docs/dashboard/knowledge/connect), so Risotto can answer from your docs.

Source: https://www.tryrisotto.com/docs/guides/initial/jira-setup-video
