# Jira Integration Permissions

Source: https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/permissions/

This page covers the roles and permissions required to configure and use the Jira integration in Qualytics.

> **Note: Two Permission Layers**
>
> Permissions for the Jira integration are split into two layers:
>
> - **Qualytics User Role** (Admin, Manager, Member) controls who can manage the integration and perform global actions.
> - **Team Permission** (Editor, Author, Drafter, Viewer, Reporter). For actions that touch a specific anomaly, the user must also have the right permission on the anomaly's datastore team.

## Integration Configuration

Actions that manage the integration itself (connecting, viewing, disconnecting).

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| View integrations list | Not allowed | Allowed | Allowed |
| View Jira integration details | Not allowed | Allowed | Allowed |
| Connect Jira integration | Not allowed | Allowed | Allowed |
| Disconnect / delete integration | Not allowed | Allowed | Allowed |
| Search Jira tickets | Not allowed | Allowed | Allowed |
| Get Jira ticket by ID | Not allowed | Allowed | Allowed |

> **Note: Single Integration**
>
> Only one ticketing integration can be active at a time. Connecting a Jira integration while ServiceNow is already connected will fail until the existing one is disconnected.

## Ticket Operations on Anomalies

Actions that create or manage links between anomalies and Jira issues. These require **both** the right user role **and** the right team permission on the anomaly's datastore.

| Action | Member | Manager | Admin | Team Permission |
| --- | --- | --- | --- | --- |
| View linked tickets on an anomaly | Allowed | Allowed | Allowed | Reporter |
| Create a Jira ticket from an anomaly | Not allowed | Allowed | Allowed | Author |
| Link an existing Jira ticket to an anomaly | Not allowed | Allowed | Allowed | Author |
| Remove a link between an anomaly and a ticket | Not allowed | Allowed | Allowed | Author |
| Change a linked issue's sync mode | Not allowed | Allowed | Allowed | Author |

> **Info: Team Permissions Hierarchy**
>
> Team permissions are hierarchical: **Editor → Author → Drafter → Viewer → Reporter**. Higher-tier permissions automatically include all lower-tier permissions. For example, a user with Editor permission automatically satisfies any action requiring Author, Drafter, Viewer, or Reporter.
>
> See [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) for details.

## How Both Layers Work Together

For ticket operations on anomalies, **both** layers must be satisfied:

1. The user must have the required **Qualytics user role** (e.g., Manager+ to create tickets).
2. The user must have the required **team permission** on the anomaly's datastore (e.g., Reporter to view, Author to link).

**Examples:**

- A **Member** with **Editor** team permission **cannot** create a Jira ticket, because Member is blocked at the user-role layer.
- A **Manager** without team membership in the datastore **cannot** create tickets for anomalies in that datastore, because they are blocked at the team layer.
- An **Admin** bypasses team permissions entirely and has full access regardless of team membership.

## UI Behavior Without Permission

| Scenario | What the User Sees |
| --- | --- |
| Member opening the Integrations page | The Integrations tab is not shown in Settings and a direct URL redirects away, so the Jira integration cannot be viewed, connected, edited, or deleted. |
| Member viewing an anomaly with linked tickets | The linked tickets list is visible (read-only) if they have Reporter permission on the datastore. |
| Member trying to create/link a ticket | The **Link or create ticket** button in the Tickets section is not shown, even with the **Author** team permission, because linking and creating tickets also require the **Manager** role. |
| Manager without team access to a datastore | Cannot create or link tickets for anomalies in that datastore even with Manager role. |

## Jira-Side Permissions

The Jira account used for the integration must have the following permissions in the target project(s):

| Permission | Purpose |
| --- | --- |
| **Browse Projects** | Read the projects and their issues, which is also how the project list is offered while connecting |
| **Create Issues** | Open issues from anomalies and from Flow actions. In a Jira Service Management project the account must also be a licensed agent |
| **Edit Issues** | Update issue fields |
| **Add Comments** | Post the mirrored comments and the status notes |
| **Edit Own Comments** | Carry an edit made in Qualytics across to the comment on the issue |
| **Delete Own Comments** | Remove the copy on the issue when the comment is deleted in Qualytics |
| **Transition Issues** | Move an issue to the mapped status. Without it, **Anomaly status sync** posts the note but the issue does not move, and the starting status chosen on the create form is not applied |

> **Note: Service projects need an agent**
>
> In a Jira Service Management project, portal customers also hold **Create Issues**, yet Jira lets only licensed agents create issues through the API. Make the integration account an agent on every service project you allow. See [Jira Service Management Projects](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/requirements/#jira-service-management-projects).

> **Note: Registering the webhook needs more**
>
> Webhooks live in Jira's system settings, so creating one requires a **Jira administrator**, not just the integration account. See [Register the Jira Webhook](https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/register-webhook/).

See [Jira Integration Requirements](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/requirements/) for the instance and account the integration needs.

> **Info: Full User Roles Reference**
>
> For the complete User Roles matrix across all Qualytics features, see the [User Roles](https://userguide.qualytics.io/settings/access/users/roles/overview/) page.

## See Also

- **How It Works**

  Data flow direction, what gets synced, when linked issues are read back, and how fields are mapped.

  [How It Works](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/how-it-works/)
- **Sync Behavior**

  What happens on each operation, from creating and linking issues to the two sync modes and comments in both directions.

  [Sync Behavior](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/sync-behavior/)
- **Requirements**

  The Jira instance, the account Qualytics authenticates as, and what it must be allowed to do.

  [Requirements](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/requirements/)
- **Best Practices**

  Reading the Tickets panel, and the choices that keep issues and anomalies in step.

  [Best Practices](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/best-practices/)

*Last updated: October 27, 2026.*