# Update Jira Ticket Sync

Move Jira ticket sync from the legacy Atlassian Connect app to the Forge app, then remove the legacy app.

> **Info:** This guide is only for organizations whose Jira integration still uses the
> legacy **Connect** app. If you set up Jira on the Forge app, or you don't sync
> tickets with Jira, you don't need it. To set up Jira for the first time, see
> [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira).

Atlassian is retiring its Connect app framework. Install the Risotto Forge app beside your Connect app. Your projects and department ticket sync settings carry over, so you don't configure them again. This guide covers Jira. For Confluence, sites shared by several Risotto organizations, and troubleshooting, see [Migrate from Connect to Forge](https://www.tryrisotto.com/docs/integrations/ticketing/migrate-connect-to-forge).

## Check which app you use

Go to **Settings > Integrations** and click the **Jira** card. On the **Jira app** card, the **Method** row shows which app syncs your tickets:

- **Connect (legacy)**: follow this guide.
- **Forge + Connect (migrating)**: the Forge app is installed. Go to [Verify and remove the legacy app](#verify-and-remove-the-legacy-app).
- **Forge**: you are up to date.

*Product example: Jira's page in the Risotto dashboard: the Jira app card's Method is Connect (legacy), with Migrate to Forge.*

## Before you start

- An Admin or a Manager in Risotto.
- An admin of your Jira site in Atlassian, to install the app.
- Your Jira site URL, for example `yourcompany.atlassian.net`.

## Install the Forge app

1. **Start the migration**

   On the **Jira app** card, click **Migrate to Forge** in the **Method** row. You can also click **Connected** and choose **Migrate to Forge...**.

2. **Confirm your Jira site**

   The **Migrate to Forge** dialog opens with the site of your Connect app in **Jira site URL**. Check the site, then click **Get install link**.

   *Product example: The Migrate to Forge dialog in the Risotto dashboard, with the Jira site URL and Get install link.*

   If Risotto cannot find the site, the dialog shows "Could not find that Jira site — check the URL and try again". If the site is already connected to another Risotto organization, the dialog says so. In that case, [contact support](mailto:support@tryrisotto.com).

3. **Open the install page**

   The dialog changes to **Install Jira Forge App**. Click **Open install page**.
   Atlassian's install page for the **risotto-jira** app opens in a new tab.

4. **Install the app in Atlassian**

   Choose your Jira site, review the permissions that the app requests, and install the app.

   *Product example: Atlassian's install page for risotto-jira, in outline, with the site picker and Install.*

5. **Return to Risotto**

   Go back to the Risotto tab. Keep the dialog open, and don't reload the page. It shows **Installing Jira Forge App** until Atlassian finishes, which can take a few minutes. When it shows **Jira Forge App Installed** ("Your Jira integration is ready to use."), click **Done**.

   Project metadata loads in the background. For a large Jira site, this can take up to 10 minutes.

## Verify and remove the legacy app

After the install, the **Method** row shows **Forge + Connect (migrating)**, and Risotto syncs tickets through the Forge app. Risotto then checks that the Forge app sees the same Jira projects and service desks as the Connect app. While it checks, the card shows "Verifying the Forge migration". When the check passes, the card shows **Forge migration verified**.

If the card shows **Forge migration verification failed**, keep the Connect app. See [Forge migration verification failed](https://www.tryrisotto.com/docs/integrations/ticketing/migrate-connect-to-forge#troubleshooting).

1. **Test the sync**

   Create a test ticket in a department that syncs to Jira, and check that the issue appears in Jira. Then add a comment on the issue in Jira, and check that it reaches the ticket in Risotto.

2. **Disconnect the legacy app**

   On the **Jira app** card, click **Connected** and choose **Disconnect legacy Connect app...**. In the confirmation, click **Disconnect**. Don't choose **Disconnect Jira (all)...**: it removes both apps and stops all Jira sync.

   *Product example: The Jira app card after the Forge app is installed: Forge migration verified, with Disconnect legacy Connect app....*

   The **Method** row now shows **Forge**.

3. **Uninstall the Connect app in Atlassian**

   Disconnecting in Risotto does not remove the Connect app from your Jira site. To remove it, uninstall the previous Risotto app in your Atlassian admin console. See [Remove the old Connect app](https://www.tryrisotto.com/docs/integrations/ticketing/migrate-connect-to-forge#remove-the-old-connect-app).

Source: https://www.tryrisotto.com/docs/guides/update-jira-sync
