# Setting up Jira as a Request Source

Turn each new issue in a Jira project into a Risotto ticket for a department, and choose which issue types and request types count

Risotto can create a ticket from each new issue in a Jira project. A Jira request source belongs to one department: the department already syncs its tickets to the project, and the issues people create there come back to Risotto as tickets for that department.

You need the Org Admin or Manager role to set this up. See [Permissions](https://www.tryrisotto.com/docs/operating/permissions).

To watch Jira connected, linked to a department and made a request source, see the [three-and-a-half-minute video](https://www.tryrisotto.com/docs/guides/initial/jira-setup-video).

## Before you start

A department can add a Jira request source when:

- The Jira app is installed. See [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira).
- The department has Jira ticket sync with a **Project** picked. Open **Settings > \<department> > Ticket Sync**, click **Add ticket sync**, pick **Jira**, and choose the project in **Configure Jira for \<department>**. See [Ticket sync](https://www.tryrisotto.com/docs/dashboard/settings/departments#ticket-sync).
- **External ticket sync enabled** is on for the department, on the same **Ticket Sync** page.
- The department's ticket sync uses the Jira site that the app is installed on.
- The department has no Jira request source yet. Each department has at most one.

## Add a Jira project

1. **Open Jira's Requests tab**

   Go to **Settings > Request Sources** and click **Manage in Jira**. Jira's page opens on its **Requests** tab.

2. **Click Add Project**

   On the **Jira projects** card, click **Add Project**. The button is unavailable, with the tip "No departments with Jira ticket sync available", when no department can add a source.

   *Product example: Jira's Requests tab in Risotto: the Jira projects card with People Ops as People's request source, and the Add Project button.*

3. **Pick the department**

   In **Add Jira Request Source**, open **Department** and pick the department. Each department is listed with the Jira project its ticket sync uses, for example **IT Department (IT Service Desk - ITSD)**.

   *Product example: The Add Jira Request Source dialog with its Department list open: IT and Security, each with the IT Service Desk project, and IT picked.*

4. **Create the source**

   Click **Create**. The project is added to the **Jira projects** card, with the department's name on its row.

Several departments can use the same Jira project, each with its own filters. Give them filters that do not overlap: an issue that matches more than one department's filters becomes one ticket, for one of those departments only.

## Choose which issues become tickets

By default, every new issue in the project becomes a ticket. Open the project's row on the **Jira projects** card to narrow that down:

- **Allowed Issue Types**: the Jira issue types that create tickets. The default is "All types allowed". When the department's ticket sync sets an **Issue Type**, the source starts with only that type, the row shows "(from dept settings)" and a lock, and you cannot change it here.
- **Allowed Request Types**: the customer request types that create tickets. The row shows only for a Jira Service Management project. The default is "All types allowed".
- **Continue over DM**: send the reporter a Slack DM when a ticket is created from this project.

1. **Open the project's row**

   On the **Jira projects** card, click the project to open its settings.

2. **Edit the filter**

   Click the edit button next to **Allowed Issue Types** or **Allowed Request Types**.

3. **Pick the types**

   Check each type that should create a ticket. **Select all** and **Select none** change every box at once. With no type checked, all types are allowed.

   *Product example: The Edit Allowed Issue Types dialog for IT Service Desk, with Service request and Incident checked, and the Save button.*

4. **Save the filter**

   Click **Save**.

When you change the allowed issue types, Risotto removes any allowed request types that no longer belong to one of them.

## What happens to a new issue

When someone creates an issue in the project and it passes a department's filters, Risotto:

- Creates a ticket in that department. The issue's summary becomes the ticket's title, and its description and attachments become the request.
- Makes the issue's reporter the requestor.
- Links the two: the ticket shows the issue key, and the issue gets a link to the ticket in Risotto.
- Posts the ticket in the department's agent channel, with its title linked to the issue.
- Starts working on the request, as it does for a chat request. Comments sync between the ticket and the issue. See [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira#features).
- Sends the reporter a Slack DM, when **Continue over DM** is on.

Only new issues become tickets. Editing an issue or changing its status does not create one.

## Disconnect a project

To stop creating tickets from a project, open its row and click **Disconnect**, then click **Disconnect** in the **Disconnect Request Source** dialog. This cannot be undone: to use the project again, add it again.

> **Warning:** Disconnecting only stops new tickets. Tickets already created from the project
> keep syncing with their issues.

Removing a department's Jira ticket sync also removes the department's Jira request source.

## Troubleshooting

### Add Project is unavailable, or a department is not listed

Check that the department:

- Has Jira ticket sync with a **Project** picked.
- Has **External ticket sync enabled** turned on.
- Syncs to the Jira site that the app is installed on.
- Does not already have a Jira request source. It is listed on the **Jira projects** card with the department's name.

### A new issue did not become a ticket

Check that:

- The issue was created after you added the project. Older issues and edits to them do not create tickets.
- The issue's type, and its request type in Jira Service Management, are allowed for the department.
- Risotto can read the reporter's email address from Jira. Without it, Risotto does not create the ticket.
- The reporter's email domain matches your [domain filter](https://www.tryrisotto.com/docs/dashboard/settings/advanced#domain-filter-regex), if you set one.
- The Jira app is still installed. See [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira#troubleshooting).

Source: https://www.tryrisotto.com/docs/operating/creating-tickets-jira
