Jira Data Center
End of life

Your Jira data. Your database. Real-time.

Export all Jira artifacts to any database in real time. Tables are created for you, every change lands in them as it happens, and Tableau or Power BI reads them directly — no export script, no nightly job.

On the Atlassian Marketplace since 2 November 2021

ETL rule: Portfolio reporting
Jira changePROJ-418 moved to Done
ETL ruleProjects, work types, fields
Your tablevl_portfolio_items

vl_portfolio_items

keystatusownerrow_updated
PROJ-410In progressa.keller09:14:02
PROJ-415In reviewm.dorn09:15:37
PROJ-418Dones.arnold09:16:11

The app creates the table from your rule and keeps writing to it after every matching change.

See it running

A connection, a rule, a table. The whole setup, click by click.

Load the interactive demo The demo is served by Supademo. Loading it transfers your IP address to Supademo; see our data protection notice.

Key features

Jira's own schema is not built for reporting. This app gives you tables that are, without anyone writing SQL or maintaining an export.

Real-time, event-driven sync

Every Jira issue change triggers an automatic update to your database tables. No batch jobs, no delays — your BI dashboards always reflect the latest data. Every row carries the Jira server it came from, so several instances can share one table.

Multi-database connections

Oracle, PostgreSQL and SQL Server, including Azure SQL. Several connections run in parallel, each routed where your BI stack needs it.

Table design without SQL

Select projects, work types and fields visually. The app works out the column types and creates the table on first activation.

Issue links exported too

Dependencies and blockers land in their own table, which is what makes traceability reporting possible at all.

Columns a BI tool can read

Tables are shaped around your fields, not Jira's internals. Connect Tableau or Power BI without a translation layer in between.

From install to first row

A Jira administrator sets this up once per reporting need. There is nothing to deploy outside Jira.

Add a database connection

Driver, JDBC URL, user and pool size, tested before it is saved. Credentials stay in your Jira instance.

Define the rule

Name it, pick the projects, move the work types and fields you want across, then point it at a connection and a schema.

Activate

The app checks whether the table exists, creates or extends it, and starts writing. Rules can be saved inactive and switched on later.

Adjust it later

Adding a field adds a column. Changing the table or the schema is handled too. Existing items can be brought in with a bulk change.

Data ETL rule

Projects

PROJPORTRISK

Work types

EpicStoryTask

Fields

SummaryStatusAssigneeDue dateCost centre

Target

PGreporting.vl_portfolio_items

Five technical columns are added automatically, including the server id and the update timestamp.

Why this app ends

Atlassian is retiring Data Center. Sales of new Data Center subscriptions and Marketplace apps ended for new customers in March 2026, and Data Center products reach end of life on 28 March 2029, when the licences and the app licences that go with them expire. The dates come from Atlassian, not from us.

This app ends with the platform it was built for. Until then it stays available and supported for existing customers, and it keeps working on current Jira releases.

Your reporting need does not end, it moves. We are building a Jira Cloud app that takes over this job, and we are happy to talk about it before you plan your migration.

Already running the app?

The documentation covers installation, database connections, ETL rules and how changes reach your tables. For anything it does not answer, the support portal is open as usual.

Developed and supported by VIP.LEAN Solutions GmbH in Germany. The app sends no data to our servers.