How the Jira Integration Works
This page explains how the Jira integration behaves under the hood — 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.
| Direction | Action | Result | Status |
|---|---|---|---|
| Qualytics → Jira | Create ticket from anomaly | New issue created with anomaly details | |
| Qualytics → Jira | Acknowledge anomaly | Comment added to issue with status change | |
| Qualytics → Jira | Archive anomaly (resolve) | Comment added to issue with resolution status | |
| Qualytics → Jira | Add comment to anomaly | Comment pushed to Jira issue | |
| Qualytics → Jira | Link existing ticket | Link stored in Qualytics only — the Jira issue is not modified | |
| Jira → Qualytics | Change issue status | Not reflected — anomaly status unchanged | |
| Jira → Qualytics | Add comments to issue | Not reflected — comments do not appear in Qualytics | |
| Jira → Qualytics | Close or resolve issue | Not reflected — anomaly remains in current state |
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:
| Field Name | Jira Field | Required | Notes |
|---|---|---|---|
| Project Key | project.key |
Yes | The Jira project where the ticket is created. Pre-filled with the Default Project Key from the integration; can be overridden per ticket. |
| Issue Type | issuetype.name |
Yes | Issue type from the project's configuration (e.g., Task, Bug, Story). |
| Summary | summary |
Yes | Brief summary of the issue (ticket title). |
| Description | description |
No | Detailed description. Anomaly context is auto-appended on submit. |
| Priority | priority |
No | Issue priority level. Standard Jira values: Highest, High, Medium, Low, Lowest. |
| Labels | labels |
No | Optional labels to categorize the issue (comma-separated tags). |
| Assignee | assignee |
No | Jira user to assign the issue to. |
Auto-Populated Fields
The following information is automatically included when creating a ticket:
| Field | Auto-Populated Value |
|---|---|
| Description | Anomaly ID, type, status at detection, field/check message, failed checks, hyperlink back to Qualytics anomaly |
| Comments (on updates) | Status changes (acknowledge, archive) and comments from Qualytics with timestamps |
Key Integration Operations
Create Ticket
Creates a Jira issue from a Qualytics anomaly with:
- Required fields:
project key,issue type,summary - Optional fields:
description,priority,labels,assignee - 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
Note
Status changes add comments but do not change the issue's status. This preserves your Jira workflow control.
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>
Supported Features & Capabilities
Current Release Features
| Feature | Status |
|---|---|
| Create Jira issue from anomaly | |
| Link existing Jira issue to anomaly | |
| Link multiple issues to one anomaly | |
| Sync anomaly acknowledge to Jira | |
| Sync anomaly archive (resolve) to Jira | |
| Push Qualytics comments to Jira as comments | |
| Hyperlink from Jira back to Qualytics anomaly | |
| Basic Authentication (email + API token) | |
| Search existing Jira issues by key or summary |
Known Limitations
| Feature | Status |
|---|---|
| Two-way sync (Jira → Qualytics) | |
| See Jira issue status changes in Qualytics | |
| Jira comments appearing in Qualytics | |
| Multiple Jira instances | |
| Change issue status from Qualytics | |
| OAuth 2.0 authentication | |
| HashiCorp Vault credential storage | |
| Automatic ticket creation from Flows |