Product

Features

Everything Fabric Link mirrors from Jira into your Fabric tenant — and the boundaries we state upfront.

live_sync

Live mirroring

Continuous issue sync with reconciliation sweeps.

Issue creates, updates, and deletes stream into your mirrored database. A five-minute reconciliation sweep catches anything a webhook missed, so analytics tables stay aligned with Jira without manual exports.

Where it appears: Mirrored tables in your Fabric workspace; sync status in Jira admin.
Limits: Webhook delivery is best-effort. The reconciliation sweep runs on a fixed interval — not real-time for every field change. Deletes are mirrored; restores depend on Jira retention.

field_selector

Field selector

Choose which Jira fields become Fabric columns.

Pick exactly which Jira fields land in Fabric — globally or per project. An analytics starter pack covers the common reporting fields so you can start fast and tighten scope later.

Where it appears: Configured in Jira admin during setup; reflected as columns in mirrored tables.
Limits: Custom field types must be supported by the mirror schema. Very wide field selections increase table size and sync time. Some computed or transient fields are excluded.

full_history

Full changelog history

Backfill field-change history from day one.

Opt-in backfill crawls every issue’s changelog, so field-change analysis starts from your project’s first day — not install day. Historical rows land in dedicated history tables ready for SQL or Power BI.

Where it appears: History tables in Fabric; backfill progress visible in Jira admin.
Limits: Backfill is rate-limited to respect Jira API quotas. Large projects can take hours or days. Issues deleted before backfill completes may have partial history.

jsm_data

JSM service data

SLA cycles, request types, and approvals alongside issues.

Service-management fields — SLA cycles, request types, approvals — export alongside issues so service reporting can live in the same Fabric workspace as delivery metrics.

Where it appears: Additional mirrored tables in Fabric for JSM entities linked to issues.
Limits: Requires Jira Service Management. Not all JSM customizations map one-to-one to Fabric columns. Asset and CMDB objects are out of scope unless explicitly enabled.

your_tenant_only

Your tenant only

Data flows to your Fabric workspace — nowhere else.

Egress is locked to Microsoft’s login, Fabric API, and OneLake endpoints. Atlassian hosts the Forge runtime; your data lands only in the Fabric workspace you authorize.

Where it appears: Enforced in the Forge app egress allowlist and Entra service principal scope.
Limits: You must provision and pay for your own Fabric capacity. Cross-tenant Fabric access is not supported. Network policies on your side can block sync if endpoints are restricted.

health_view

Health and operations

Mirroring status, watermarks, and dead-letter replay.

Per-table mirroring status, backfill progress, watermarks, and a replayable dead-letter queue — all inside Jira admin so operators can see what landed and what needs attention.

Where it appears: Jira admin → Fabric Link health view.
Limits: Dead-letter replay is manual. Health metrics reflect the mirror’s view, not Fabric query performance. Alerting integrations are not included — export logs to your SIEM if required.