Jira

Create Jira issues from Validio incidents using a Jira integration and channel.

The Jira integration lets Validio create Jira issues for data quality incidents, source errors, and other events, so your team can triage data problems in the same tracker you already use.

Validio supports Jira Cloud and Jira Data Center. You configure the connection once as an integration and then create one or more notification channels that route alerts to specific projects and issue types.

Prerequisites for Adding a Jira Integration

Before creating the integration in Validio, you will need the following in Jira:

  • A Jira account with permission to create issues in the target project.
  • A Base URL for your Jira instance, for example https://your-account.atlassian.net.
  • Authentication credentials. The supported authentication types depend on your Jira platform:
    • Jira Cloud — use Basic Auth (email address + API token) or Service Account (service account API token).
    • Jira Data Center — use Personal Access Token (PAT issued in Jira) or OAuth 2.0 Client Credentials (client ID + client secret).
  • A Webhook secret that you set in Validio and reuse when configuring Jira to send status updates back to Validio.
  • A Project key and Issue type (for example, DATA and Bug) for each channel you plan to create.

Create a Jira Integration

To add a new Jira integration in Validio:

  1. Navigate to Workspace > Integrations and click + New integration.
  2. From the Integration type list, select Jira.
  3. Enter a Name that describes the integration, for example "Atlassian Cloud".
  4. Under Configuration, enter the Base URL and select the Platform (Cloud or Data Center).
  5. Enter a Webhook secret. This secret is used to authenticate status updates sent from Jira back to Validio.
  6. Under Authentication, select the Authentication type and complete the matching fields. The dropdown only shows the auth types valid for the selected platform: Basic Auth and Service Account for Cloud, Personal Access Token and OAuth 2.0 for Data Center. Switching the Platform after selecting an auth type resets the auth type to a valid option for the new platform. Refer to Jira Configuration Parameters.
  7. (Optional) Click Test integration to verify the connection to Jira.
  8. Click Create integration.

Jira integration configuration with authentication options

Jira Configuration Parameters

FieldDescription
Base URLURL of your Jira instance. For Jira Cloud, this typically ends in .atlassian.net.
PlatformChoose Cloud or Data Center based on your Jira deployment. The selected platform filters which authentication types are available.
Webhook secretSecret value that Validio uses to authenticate incoming webhook requests from Jira.
Authentication typeThe available options depend on the selected platform. Cloud: Basic Auth or Service Account. Data Center: Personal Access Token or OAuth 2.0.
Email(Basic Auth) The email address of the Jira account Validio will authenticate as.
API token(Basic Auth or Service Account) The API token generated in Jira for the account.
Personal access token(Personal Access Token) The PAT string generated in Jira.
Client ID(OAuth 2.0) The client ID of the Jira OAuth 2.0 client credentials.
Client secret(OAuth 2.0) The client secret of the Jira OAuth 2.0 client credentials.

Create a Validio Channel for Jira

Jira channel and default rule configuration

After the integration is created, create a channel that routes notifications to a specific Jira project and issue type.

  1. In Validio, navigate to Notifications > Channels and click + New channel.
  2. Select the Namespace where the channel will live. Only users with access to this namespace can see or use the channel.
  3. Under Integration, select the Jira integration you just created.
  4. Enter a Name for the channel that describes its purpose, for example "Data Quality Bugs".
  5. Under the Jira-specific settings, choose the Project and Issue type. Both fields are dropdowns that load options directly from your Jira instance. If discovery fails (for example, due to invalid integration credentials), the form shows a banner explaining the failure and falls back to plain text inputs so you can still enter the values manually, for example DATA and Bug. If you see the failure banner, verify the integration's credentials on Workspace > Integrations and reopen the channel dialog.
  6. (Optional) Add a Default notification rule. You can add more rules and conditions later.
  7. Click Create.

After the channel is created, add notification rules from the channel's details page to control which incidents create Jira issues.

Next Steps

  • Add notification rules on the channel's details page to filter which incidents create Jira issues. See Adding Notification Rules.
  • Review existing integrations and channels under Workspace > Integrations and Notifications > Channels.
  • If you use Jira Data Center with an on-premises deployment, you can add multiple Jira integrations to route to separate instances.