Documentation

Assets to SQL for Jira Service Management

Last updated: August 26, 2026

Overview

Assets to SQL transforms your Jira Assets (CMDB) data into relational SQL dumps (PostgreSQL-compatible), CSV files and JSON for use in BI tools like eazyBI, Power BI, Tableau, or Metabase. It walks your schemas — cross-schema references included — flattening the Assets object hierarchy into proper SQL tables with inlined reference attributes and handling multi-value fields (either flattened or as junction tables), and supports scheduled exports served through an authenticated REST pull endpoint. The bundled Assets SQL Filter dashboard gadget then queries those exports live on any Jira dashboard, with guided joins, AND/OR filters and a validated SELECT-only SQL mode. The app runs natively on Atlassian Forge — the relational store is Forge SQL inside your own tenant, so there is no external database and no server to operate.

Prerequisites

Jira site requirements

Jira Cloud site with any paid JSM plan. Since February 2026 Assets is included on Standard (5,000-object allowance), Premium (50,000) and Enterprise — the app works identically on all three.
At least one Assets schema with some objects already created.
A one-time, per-schema role grant: add "Assets to SQL for Jira" to each schema's Users role in Assets (read-only, the standard app-account model — the same one eazyBI and Automation use). The app detects a missing grant and guides you through it.
The logged-in user must have permission to read Assets data.

Limits

50,000 objects per export. Larger datasets complete as partial, labelled explicitly rather than silently truncated.
Exports run up to 15 minutes in the background, with live progress and a cancel button.
Stored artifacts are capped at roughly 100 MB per format.
The file export uses the PostgreSQL dialect; it imports into most engines with minimal changes.
Pull-endpoint CSV is base64-wrapped — a Forge platform constraint.
Dashboard gadget data reflects the last export, not live Assets, and every gadget is labelled "data as of".

License

The app requires an active license. During Marketplace review, the evaluation license provided by the review process is sufficient.

Installation

Install the app from the Atlassian Marketplace listing onto your Jira Cloud site.
Open the app via Apps → Assets to SQL for Jira. It registers as a Jira Global Page.
The app loads with six tabs: Dashboard, Configure, Export, Settings, Sync History, Help.

Testing Instructions (for Marketplace Reviewers)

Configure tab — 3-step wizard

Click the "Configure" tab. You will see a 3-step progress tracker: Select Schemas → Select Object Types → Configure Attributes.

Step 1: Select Schemas

Check the box next to one or more schemas, then click "Next".

Step 2: Select Object Types

Review the listed object types and uncheck any you don't want to export. Click "Next".

Step 3: Configure Attributes

Click each object type button to review its attributes. For multi-value attributes choose either "Flatten (comma-separated)" or "Junction table" mode. Click "Save Configuration".

Settings tab — Schedule and Pull Endpoint

Configure scheduled sync and generate an API key for the pull endpoint. Click "Save Settings".

Testing each major feature

First export (manual)

Complete the Configuration wizard. Go to the Export tab, select "CSV Zip" + "Download from UI", and click "Export Now". A progress bar appears; when complete, download the ZIP.

SQL export and schema preview

Select "SQL Dump (PostgreSQL)" and click Export Now. Use "Preview Schema" on the Configure tab to see generated DDL.

Dashboard overview

Shows last sync timestamp, trigger type, status, row count, duration, plus a table breakdown.

Sync History

Table of the last 20 sync entries with expandable details.

Scheduled sync

Toggle on, set frequency, and save. Uses the same export pipeline as manual exports.

Pull endpoint (BI tool integration)

Generate a 256-bit API key (shown once — copy it immediately) and authenticate with a Bearer token. Returns JSON — full, or per-table flat arrays, the shape eazyBI maps directly — or base64-wrapped CSV. Settings lists a ready-made per-table source URL for every exported table, and a pull activity log records each fetch with time, table and row count.

Multi-value attribute handling

Choose "Junction table" mode to create a separate link table per multi-value attribute, or "Flatten" to keep them as comma-separated strings.

Assets SQL Filter gadget (dashboards)

Before a table can be queried on a dashboard an admin must expose it — nothing is queryable by default, because dashboards reach broad audiences. Once exposed, add the Assets SQL Filter gadget to any Jira dashboard and edit it:

Basic mode — pick a table, join related tables along real relations in both directions, choose and rename columns, chain AND/OR conditions, and sort.
SQL mode — write a SELECT statement (LEFT JOIN, WHERE with AND/OR and parentheses, LIKE/CONTAINS, IS NULL, ORDER BY, LIMIT, AS aliases). Click Validate: the statement is parsed and checked against the stored schema before anything runs. "Show SQL" reveals the exact query behind any view.
Filter controls — expose up to four columns as viewer-facing dropdowns (populated from live values) or text search.

Text matching is case-insensitive; numbers and dates compare exactly. Every gadget displays a "data as of" label reflecting the export it reads — gadget data is not live Assets.

Troubleshooting

Symptom	Cause	Fix
"No schemas found" in Step 1	Assets is not enabled, no schemas exist, or the app's account has no role grant	Verify JSM Standard or above with Assets enabled. Create a schema with at least one object type, and add "Assets to SQL for Jira" to the schema's Users role.
A schema is missing from the list	The per-schema role grant is missing for that schema	In Assets, add the app's account to that schema's Users role (read-only). The grant is per schema, not global.
Export returns 0 objects	Object types are selected but contain no objects	Verify the selected object types have actual objects.
Export status shows "Partial"	More than 50,000 objects across all selected types, or the 15-minute window elapsed	Reduce the number of selected schemas or object types. Partial exports are labelled, never silently truncated.
Pull endpoint returns 401	Missing, invalid or revoked API key	Generate a key in Settings and send it as a Bearer token. Keys are shown once — regenerate if lost.
Gadget shows no tables to pick	No tables have been exposed for dashboard use	In Settings, expose the tables you want queryable. Exposure is opt-in per table by design.
Gadget data looks out of date	Gadgets read the last export, not live Assets	Run an export or enable a scheduled sync. The gadget's "data as of" label shows which export it is reading.

Support

For support enquiries: support@3t-apps.com

Support hours: Monday–Friday, 9:00 AM–5:00 PM CET. Target response time: 1 business day.

Visit Support page → · View full SLA →