Collaboration connector

The Jira data catalog your whole team can trust.

The Dawiso Jira integration links every cataloged asset to its tickets: bugs, change requests, access requests, DQ incidents, with status visible inside Dawiso.

Read the docs

Live connector Stable connector

Jira

Dawiso

Metadata-only · your data never leaves the source

Type: Issue tracking & project management
Auth: Atlassian API token + JQL
Sync: On-demand lookup + embedded tickets
Direction: Read-only · metadata

First things first

What is a data connector?

Metadata-only Read-only access Incremental sync Cross-system lineage

A data connector is the bridge between a tool in your stack and the catalog that gives you a unified view of it. Once a connector is configured, it reaches into the source system on a schedule, reads out the metadata - schemas, tables, dashboards, jobs, ownership, lineage - and represents it inside the catalog. Your actual rows and values stay where they are.

Connectors are the reason a data catalog can answer questions like "which Power BI dashboard depends on this Snowflake table?" or "who owns the orders topic in Kafka?" - automatically, without anyone keeping a spreadsheet up to date.

Three properties separate a good connector from a brittle one: it should be read-only and safe, it should be incremental so a full re-scan isn't required for every refresh, and it should resolve lineage across system boundaries, not just inside one tool.

About the platform

What is Atlassian Jira?

Atlassian Jira is the issue-tracking tool that grew up with software teams and now runs change management, incident response and governance backlogs across whole companies. Data, IT, security and product teams use it to coordinate work, file bugs, and track who is on the hook for what.

Data tickets live where the rest of work already lives: in Jira. The problem is that the ticket and the data asset it refers to never sit next to each other. Analysts trade Slack screenshots. Stewards copy-paste table names into JQL. That's where the Dawiso Jira integration joins the picture: every business term, table, report or DQ rule in Dawiso links to its open and closed Jira tickets, and DQ incidents can open new ones with one click.

Architecture

How Dawiso connects to Jira

A small read-only role on the Jira side. The Dawiso scanner pulls metadata on a schedule. Everything ends up in your catalog, business-readable.

Source

Atlassian Jira

Issues & projects
JQL queries & filters
Custom fields
Ticket status & resolution

REST · JDBC

Dawiso scanner

Read-only metadata

Schema & object discovery
Dependency resolution
SQL flow parsing (optional)
Sampling on opt-in

Internal

Catalog

Dawiso platform

Searchable metadata
Lineage & ownership
Business glossary
Policy & classifications

Connection details

Protocol: Jira REST API + JQL queries from Dawiso editor
Authentication: Atlassian account · API token · project-scoped permissions
Lineage: Jira tickets attach to Dawiso assets (terms, tables, reports, DQ rules); status and resolution flow back into the catalog without a sync job

Setup

Connect Jira in 4 steps

01

Create an Atlassian API token

In your Atlassian account, generate a token scoped to the Jira projects Dawiso should read. Use a dedicated service account if your org policy requires it.
02

Configure the Jira integration

Add the Jira base URL, service account email and API token in Dawiso. Pin the default project key (e.g. DATA) used for new DQ incident tickets.
03

Map object attributes to Jira fields

Set object attributes (owner, domain, sensitivity) as filterable Jira fields. Now JQL searches inside Dawiso can pivot on governance attributes.
04

Embed and look up tickets

From any Dawiso text editor, type / and pick Jira integration to embed a ticket by ID. From any object, click the Jira icon to look up issues matching the object name.

Capabilities

What you get with the Jira connector

Embed tickets in any object

Type / inside a Dawiso editor and pick Jira integration. Add tickets by ID, by paste, or by picking from a list. Status renders inline.
Auto-lookup matching issues

Click the Jira icon on any object: Dawiso lists every Jira issue whose name matches, with editable JQL to narrow by project, label or date.
DQ incidents to Jira tickets

A failed DQ rule creates a Jira ticket with the rule, the affected asset and the owner. Tracking moves to the team's existing board.
Owner and assignee parity

Dawiso asset owner and Jira assignee stay in sync via the linked ticket. No more 'who's actually fixing this' meetings.
Attribute-driven JQL

Object attributes become Jira fields. Filter tickets by data domain, sensitivity or steward without leaving the catalog.
Audit trail for compliance

Every metadata change can carry an associated Jira ticket. Auditors see the data change and the approved ticket side by side.

Business value

Why teams turn on the Jira connector

0 tabs
Tickets next to the data

Analysts read the Jira status of every dataset and report without switching tools. Context that used to need three tabs is on one page.
Same board
DQ work where teams already plan

Data quality incidents become Jira tickets on the team's existing sprint board. No second backlog, no parallel governance tool.
Audit-ready
Change with evidence

Every cataloged term, table and rule carries the ticket that approved its last change. Auditors see the trail without screenshots.

Ready to catalog your Jira?

Set up the connector in an afternoon. See your first lineage graph the same day.

Read the docs

Frequently asked questions

Still curious? Talk to our team ->

Does Jira have a data catalog?

No. Jira tracks issues and projects. Dawiso reads Jira metadata read-only and links issues to the data assets, glossary terms and pipelines they relate to, keeping governance work connected to the catalog.

What is the purpose of a data catalog?

A data catalog makes data assets discoverable, documented and trustworthy. Dawiso connects Jira issues and projects to the datasets they govern, so requests, owners and decisions stay linked to the data they affect.

Does Dawiso replace Jira?

No. Dawiso links to Jira; tickets stay in Jira and are managed there. The integration adds context: each Dawiso object knows its tickets, and DQ incidents can open new ones without leaving the catalog.

Which Jira editions are supported?

Jira Cloud and Jira Data Center are both supported via the Atlassian REST API. The integration uses a dedicated Atlassian account with an API token; on-prem Jira works through Dawiso Integration Runtime.

What permissions does the Jira account need?

Read access to the projects Dawiso should index, plus permission to create issues in the projects used for DQ incident tickets. Least-privilege scoping is recommended: a dedicated service account, not a personal one.

Can I filter tickets by data attributes?

Yes. Map Dawiso object attributes (owner, domain, sensitivity) to Jira custom fields. JQL queries from inside Dawiso can then filter by governance attributes, not just by free text.