fabriclink

Features

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

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 Live mirroring appears and its limits
Detail
Where it appearsMirrored tables in your Fabric workspace. Sync status in Jira admin.
LimitsWebhook delivery is best-effort. The reconciliation sweep runs on a fixed interval, so not every field change is real-time. Deletes are mirrored. Restores depend on Jira retention.

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 Field selector appears and its limits
Detail
Where it appearsConfigured in Jira admin during setup. Reflected as columns in mirrored tables.
LimitsCustom 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 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 rather than install day. Historical rows land in the changelog table ready for SQL or Power BI.

Where Full changelog history appears and its limits
Detail
Where it appearsThe changelog table in Fabric. Backfill progress in Jira admin.
LimitsBackfill 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 service data

SLA cycles, request types and approvals alongside issues

Service-management fields export alongside issues so service reporting can live in the same Fabric workspace as delivery metrics.

Where JSM service data appears and its limits
Detail
Where it appearsAdditional mirrored tables in Fabric for JSM entities linked to issues.
LimitsRequires Jira Service Management. Not all JSM customisations map one-to-one to Fabric columns. Asset and CMDB objects are out of scope unless explicitly enabled.

Your tenant only

Data flows to your Fabric workspace and 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 authorise.

Where Your tenant only appears and its limits
Detail
Where it appearsEnforced in the Forge app egress allowlist and the Entra service principal scope.
LimitsYou 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 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 Health and operations appears and its limits
Detail
Where it appearsJira admin, Fabric Link, Health tab.
LimitsDead-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.