Skip to content

Jira Integration Requirements

What has to exist on the Jira side before the integration can be connected, and what the account Qualytics authenticates as needs to be able to do.

The Jira Instance

Requirement Details
Jira Cloud The integration talks to the Jira Cloud REST API. A Jira Data Center or Server instance is not supported.
Instance URL The full site URL, in the form https://your-domain.atlassian.net, with no trailing slash.
API access The REST API has to be reachable from the deployment. A self-hosted Qualytics behind a firewall needs outbound access to the Jira site.
Projects At least one project the integration may create issues in. You pick them while connecting, from the list Qualytics reads out of Jira.

The Integration Account

Qualytics authenticates as one Jira account and acts on its behalf: every issue it creates, every comment it posts, and every transition it runs is attributed to that account. A dedicated service account is easier to recognize in the issue history than a person's own login.

Value Details
Email The email address of the Atlassian account.
API token A token generated from that account's Atlassian settings. See Jira Configuration.
Format The two are entered together as email:api_token, which is what the Credentials field expects.

Changing the account later

The credentials can be replaced at any time from the edit modal, and issues created by the previous account keep their history. See Edit Jira Connection.

Permissions in Jira

The account needs permission in every project you allow, not only the default one. The full list, and what each permission is for, is on the Permissions page.

Registering the webhook is the one step that asks for more than the integration account. Webhooks live in Jira's system settings, so a Jira administrator creates it. See Register the Jira Webhook.

See Also

  • Best Practices

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

    Best Practices

  • Permissions

    The roles, team permissions, and Jira-side permissions each action needs.

    Permissions

  • How It Works

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

    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