How the Jira Integration Works

This page explains how the Jira integration behaves internally: how data flows between Qualytics and Jira, what is synced, and how fields are mapped.

Integration Flow Diagram

The following diagram illustrates how data flows from Qualytics to Jira:

flowchart TB
    subgraph Qualytics["Qualytics Platform"]
        A[Anomaly Detected] --> B{User Action}
        B -->|Create Ticket| C[Create Ticket Request]
        B -->|Acknowledge| D[Status Change Event]
        B -->|Add Comment| E[Comment Event]
        B -->|Archive/Resolve| F[Resolution Event]
    end

    subgraph Background["Background Processing"]
        C --> G[Qualytics API]
        D --> H[Sync Worker]
        E --> I[Sync Worker]
        F --> J[Sync Worker]
    end

    subgraph Jira["Jira Instance"]
        G -->|POST /issue| K[New Issue Created]
        H -->|POST /comment| L[Comment Added]
        I -->|POST /comment| L
        J -->|POST /comment| M[Resolution Comment]
    end

    K --> N[Ticket Link Stored]
    N --> O[Anomaly & Issue Linked]

What Gets Synced

The current release supports one-way synchronization from Qualytics to Jira.

Authentication

The Jira integration uses Basic Authentication with an email address and an API token (formatted as email:api_token). The API token is generated from Atlassian account settings and grants Qualytics the ability to act on behalf of the account.

See the Configure Jira and Add Connection guides for the full setup flow.

Field Mapping Reference

Issue Fields Supported

When creating a ticket from Qualytics, the following Jira issue fields can be populated:

Two values are not part of the form and cannot be set per ticket:

• Project: every issue is filed in the Default Project Key configured on the integration.
• Issue type: every issue is created as a Task.

Labels and assignee are neither offered in the form nor sent to Jira. Set them in Jira after the issue is created.

Auto-Populated Fields

The following information is automatically included when creating a ticket:

Key Integration Operations

Create Ticket

Creates a Jira issue from a Qualytics anomaly with:

• Required field: summary
• Optional fields: description, status, priority
• Set by the integration: the project (Default Project Key) and the issue type (Task)
• Auto-included: Anomaly ID, status, type, failed checks, and hyperlink back to the Qualytics anomaly (appended to the description)

Link Existing Ticket

Links an existing Jira issue to an anomaly:

• Creates the association between the anomaly and the Jira issue in Qualytics
• Does not modify the Jira issue: no comment is added and the issue content stays untouched

Sync Anomaly Status

When anomaly status changes in Qualytics:

• Adds a timestamped comment to the linked Jira issue
• Example: [2024-01-15 10:30:00 UTC] Qualytics Anomaly Status: Acknowledged

Sync Comments

When comments are added to anomalies in Qualytics:

• The comment text is synced to linked tickets as Jira comments
• Example: Comment from Qualytics: <user's comment>

The comment arrives as plain text, so a mention shows up as a raw text code rather than as the formatted name you saw when typing it, and the mentioned user is notified in Qualytics only. A reply arrives as its own Jira comment with no indication of which comment it answers, because Jira comments are a flat list. The anomaly's Timeline in Qualytics keeps the full thread with its structure.

Supported Features & Capabilities

Current Release Features

Known Limitations