# Edit Jira Connection

Source: https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/edit-connection/

Change the Jira integration after it is connected: the instance URL, the credentials, the projects Qualytics may write to, the issue type it creates in each, and how much it syncs. The edit modal is also the only place the webhook URL is shown.

> **Info: Permissions**
>
> Users with the **Manager** or **Admin** role can edit the Jira integration. See the [Permissions](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/permissions/) page for details.

## What You Can Change

Every field on the connection form can be changed here, and each one behaves as it does when connecting. See the [Field reference](https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/add-connection/#fields) in Add Connection for what each one holds. What differs is what follows the save.

| Change | What follows |
| --- | --- |
| **Credentials** | The stored value is never shown again, so the field stays masked. Leave it untouched to keep the current credentials, or click **Edit**  inside it to replace them. Qualytics tests the new value against the instance before saving. |
| **Instance URL** | Tested the same way. The links already stored keep the addresses they were created with, so their issue key link still opens the old site. Point the integration at a different site only when the issues you have linked live there too. |
| **Allowed Projects** | Issues can only be created in the projects on the list, and searching for an issue to link is scoped to it as well. An issue already linked from a project you remove stays linked and keeps syncing. |
| **Issue Type** | Applies to the issues created after the save. Issues already in Jira keep their type. A project you add to **Allowed Projects** starts on `Task` until you pick another type. |
| **Sync Settings** | Applied from the next event onward. Nothing is re-sent or replayed for what happened while the previous setting was in force. |

The **Webhook URL** box appears here and not on the add form, because the URL is minted for an integration that already exists. Editing the integration does not change it, so a webhook already registered in Jira keeps working.

## Steps

**Step 1**: In the left side panel, click **Settings** .

**Step 2**: The **Connections** tab opens by default. Click the **Integrations** tab.

**Step 3**: Find the **Jira** row, which shows **Connected** and your instance URL, and click the **vertical ellipsis**  next to the status.

**Step 4**: Click **Edit**  in the menu. The **Edit Jira Integration** modal opens with the current values already filled in.

**Step 5**: Change what you need. To replace the credentials, click the **Edit**  control inside the masked **Credentials** field and type the new `email:api_token` value.

**Step 6**: To register or re-register the webhook, find the **Webhook URL** box and click **Copy** . The steps for the Jira side are on [Register the Jira Webhook](https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/register-webhook/).

**Step 7**: Click **Update**. A success message appears and the **Jira** row shows the new details. When you changed the instance URL or the credentials, Qualytics tests them against Jira before saving, so a rejection stops the update. Changing only the projects, their issue types, or the sync settings is saved without that test.

> **Note**
>
> A rejected test fails the update with an error and keeps the previous values, so the integration is never left half-changed.

*Last updated: October 27, 2026.*
