Decube
Try for free
  • 🚀Overview
    • Welcome to decube
    • Getting started
      • How to connect data sources
    • Security and Compliance
    • Data Policy
    • Changelog
    • Public Roadmap
  • Support
  • 🔌Data Warehouses
    • Snowflake
    • Redshift
    • Google Bigquery
    • Databricks
    • Azure Synapse
  • 🔌Relational Databases
    • PostgreSQL
    • MySQL
    • SingleStore
    • Microsoft SQL Server
    • Oracle
  • 🔌Transformation Tools
    • dbt (Cloud Version)
    • dbt Core
    • Fivetran
    • Airflow
    • AWS Glue
    • Azure Data Factory
    • Apache Spark
      • Apache Spark in Azure Synapse
    • OpenLineage (BETA)
    • Additional configurations
  • 🔌Business Intelligence
    • Tableau
    • Looker
    • PowerBI
  • 🔌Data Lake
    • AWS S3
    • Azure Data Lake Storage (ADLS)
      • Azure Function for Metadata
    • Google Cloud Storage (GCS)
  • 🔌Ticketing and Collaboration
    • ServiceNow
    • Jira
  • 🔒Security and Connectivity
    • Enabling VPC Access
    • IP Whitelisting
    • SSH Tunneling
    • AWS Identities
  • ✅Data Quality
    • Incidents Overview
    • Incident model feedback
    • Enable asset monitoring
    • Available Monitor Types
    • Available Monitor Modes
    • Catalog: Add/Modify Monitor
    • Set Up Freshness & Volume Monitors
    • Set Up Field Health Monitors
    • Set Up Custom SQL Monitors
    • Grouped-by Monitors
    • Modify Schema Drift Monitors
    • Modify Job Failure Monitors (Data Job)
    • Custom Scheduling For Monitors
    • Config Settings
  • 📖Catalog
    • Overview of Asset Types
    • Assets Catalog
    • Asset Overview
    • Automated Lineage
      • Lineage Relationship
      • Supported Data Sources and Lineage Types
    • Add lineage relationships manually
    • Add tags and classifications to fields
    • Field Statistcs
    • Preview sample data
  • 📚Glossary
    • Glossary, Category and Terms
    • Adding a new glossary
    • Adding Terms and Linked Assets
  • Moving Terms to Glossary/Category
  • AI Copilot
    • Copilot's Autocomplete
  • 🤝Collaboration
    • Ask Questions
    • Rate an asset
  • 🌐Data Mesh [BETA]
    • Overview on Data Mesh [BETA]
    • Creating and Managing Domains/Sub-domains
    • Adding members to Domain/Sub-domain
    • Linking Entities to Domains/Sub-domains
    • Adding Data Products to Domains/Subdomains
    • Creating a draft Data Asset
    • Adding a Data Contract - Default Settings
    • Adding a Data Contract - Freshness Test
    • Adding a Data Contract - Column Tests
    • Publishing the Data Asset
  • 🏛️Governance
    • Governance module
    • Classification Policies
    • Auto-classify data assets
  • ☑️Approval Workflow
    • What are Change Requests?
    • Initiate a change request
    • What are Access Requests?
    • Initiate an Access Request
  • 📋Reports
    • Overview of Reports
    • Supported sources for Reports
    • Asset Report: Data Quality Scorecard
  • 📊Dashboard
    • Dashboard Overview
    • Incidents
    • Quality
  • ⏰Alert Notifications
    • Get alerts on email
    • Connect your Slack channels
    • Connect to Microsoft Teams
    • Webhooks integration
  • 🏛️Manage Access
    • User Management - Overview
    • Invite users
    • Deactivate or re-activate users
    • Revoke a user invite
  • 🔐Group-based Access Controls
    • Groups Management - Overview
    • Create Groups & Assign Policies
    • Source-based Policies
    • Administrative-based Policies
    • Module-based Policies
    • What is the "Owners" group?
  • 🗄️Org Settings
    • Multi-factor authentication
    • Single Sign-On (SSO) with Microsoft
    • Single Sign-On (SSO) with JumpCloud
  • ❓Support
    • Supported Features by Integration
    • Frequently Asked Questions
    • Supported Browsers and System Requirements
  • Public API (BETA)
    • Overview
      • Data API
        • Glossary
        • Lineage
        • ACL
          • Group
      • Control API
        • Users
    • API Keys
Powered by GitBook
On this page
  • Set up Jira connection
  • Syncing Statuses from Decube to Jira
  • Adding Jira Sync Webhook to Decube
  • Creating Issues from Decube to Jira
  • Modifying a Jira Issue
  • Unlinking Jira Issues from Decube
  • Disconnecting Jira from Decube
  1. Ticketing and Collaboration

Jira

Integrating Decube with Jira allows you to create issue tickets directly on the detected incidents, streamlining your workflow and ensuring efficient incident management.

PreviousServiceNowNextEnabling VPC Access

Last updated 1 month ago

Prerequisites

  1. An active Decube account with the necessary permissions to configure integrations.

  2. A Jira account with administrative privileges or the required permissions to create and manage issues.

The authentication credentials is different between Jira Cloud and Jira Data Centre. Please refer to the correct section for required step for each version.

Set up Jira connection

  1. Log in to your Decube account and navigate to the "Integrations" section under "My Account" page.

  2. Locate the "Jira" integration and click on the "Connect" button as below.

  1. Select your Infrastructure. There are 2 options, which depend on your organization's Jira setup: Cloud and Data centre.

Option 1: Jira Cloud

  1. After selecting Jira Cloud option, you will need to provide the Server URL. This can be found in your workspace console settings, eg. https://your-domain.atlassian.net.

  2. Provide the Jira account email which was used to generate the API token above.

Once these information is provided, click on Proceed to connect.

Option 2: Data Center

  1. After selecting Jira Data Center option, you will need to provide the Server URL. This can be found in your workspace console settings, eg. https://your-domain.atlassian.net.

  2. Provide the Jira Account Username which was used to generate the Personal Access Token above.

Once these information is provided, click on Proceed to connect.

After successful authentication, you will see that the button to Connect to Jira now changes to: Disconnect and Manage.

Syncing Statuses from Decube to Jira

To Sync statuses from your Jira Project to Decube, Select the "Manage" option.

Add a project to begin mapping your Jira Statuses from the selected project to Decube's Statuses.

Upon Selecting a project, select "+ Map Issue".

Choose the Issue Type, Issue Status, and the corresponding Incident Status in Decube that you want to map.

Adding Jira Sync Webhook to Decube

To sync statuses from Jira to Decube and automatically close incidents, you will need to add following Jira Sync Webhook URL to your Jira account.

The steps for managing webhooks in your Jira account differs from Jira Cloud and Jira Data Centre. Please refer to the correct guide for each Manage Webhook flow:

Creating Issues from Decube to Jira

To create an issue in Jira from Decube, go to the Data Quality module and select an incident. In the Incident Details Page, you will find an option to create a Jira issue.

In the "Create a Jira Issue" pop-up, the user must fill out the following fields:

  • Choose an Issue Type

  • Add an Assignee

  • Enter a Summary

  • Provide a Description

Complete the process by selecting "Create This Issue." You have successfully created an issue from Decube to Jira. You can now view the following details:

  • Issue Title

  • Issue ID

  • Assignee

  • Issue Status

  • Options to Unlink or Modify the Jira Issue.

Modifying a Jira Issue

To Modify a Jira issue, select the "Pencil" icon on the generated Jira Issue.

Users are allowed to modify the fields below except Projects and Issue Type.

Unlinking Jira Issues from Decube

To unlink a Jira Issue from Decube, select the "Unlink" option from the generated Jira Issue ticket.

On the confirmation prompt, select "Unlink" to unlink you Issue from Decube.

When you unlink a Jira issue, Decube will stop syncing any update statuses for that issue. However, you can relink the issue at any time to resume syncing the latest status from Jira.

Disconnecting Jira from Decube

To Disconnect Jira, navigate to My Account > Integrations > Jira and simply select the "Disconnect" option.

Select "Yes, Disconnect" to Disconnect Jira from Decube.

When you disconnect Jira from Decube, all generated Jira issue tickets will be revoked. However, you can reconnect to Jira at any time.

You will then need to generate an API token from your Atlassian account. This is the on how to create the API token.

You will then need to generate an Personal Access Token from your Atlassian account. This is the on how to create the API token.

Jira Cloud:

Jira Data Centre:

Select a Project (based on the projects previously mapped )

🔌
Atlassian guide
Atlassian guide
link to Atlassian documentation
link to Atlassian documentation
here
You will need to generate the API token and give the Jira account email to authenticate access.
You will need to generate a PAT and give the Jira account username to
Jira Credentials Successfully Authenticated State.