Skip to content

Jira Introduction

The Jira integration enables data quality teams to create and link Jira issues directly from data anomalies detected in Qualytics. This streamlines the issue resolution workflow by eliminating the need to manually create tickets in Jira and then reference them back in Qualytics.

Key Benefits

  • Create Issues Directly: Create Jira issues directly from Qualytics anomalies without leaving the platform
  • Automatic Linking: Automatic linking between anomalies and tickets for complete traceability
  • Cross-Reference Linking: Each Jira issue contains a hyperlink back to its source anomaly in Qualytics
  • Status Synchronization: Anomaly status changes (acknowledge, archive) are posted to Jira, and issue status and summary are read back onto the anomaly's ticket card
  • Comment Syncing: Comments travel both ways: pushed from Qualytics onto the issue naming their author, and mirrored from the issue onto the anomaly's timeline, with edits and deletions following along

Integration Type

The integration syncs two ways by default. Qualytics posts comments and status notes to linked issues, and reads issue status, summary and comments back onto the anomaly. With Anomaly status sync turned on, statuses move together through a mapping you configure. The integration, or any single linked issue, can also be set to Read only so nothing is written to Jira. See Read only and two-way sync.

Permissions

Users with the Manager or Admin role can configure the Jira integration in Qualytics. See Permissions for details.


Deep Dive

Understand how the Jira integration works internally: data flow, behavior, and field mapping.

  • How It Works


    Data flow direction, what gets synced, field mapping, and key operations.

    How It Works

  • Sync Behavior


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

    Sync Behavior

  • Requirements


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

    Requirements

  • Best Practices


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

    Best Practices

  • Permissions


    Roles required to configure and use the Jira integration.

    Permissions


How-tos

Set up the integration. Opening, linking, and unlinking tickets happens on the anomaly, so those steps live under Anomalies.

  • Jira Configuration


    Generate an API token and gather the values needed for Qualytics.

    Jira Configuration

  • Add Jira Connection


    Connect the Jira integration in Qualytics.

    Add Jira Connection

  • Edit Jira Connection


    Update the instance URL, credentials, allowed projects, or sync settings.

    Edit Jira Connection

  • Disconnect Jira


    Remove the Jira integration, and with it every anomaly-ticket link.

    Disconnect Jira

  • Register the Jira Webhook


    Register the Qualytics webhook in Jira so ticket changes arrive within seconds.

    Register the Jira Webhook


Reference

  • Troubleshooting


    Symptoms, causes, and resolutions for freshness, status sync, comments, and setup.

    Troubleshooting

  • API


    The ticketing and anomaly ticket link endpoints, with sample requests.

    API

  • FAQ


    Common issues with authentication, permissions, project access, ticket creation, and sync behavior.

    FAQ