Fields & project scope
Control what lands in Fabric: which fields become columns and which projects are in scope.
Field selection
Open Jira admin → Fabric Link → Field selector.
A curated analytics starter pack is selected by default — status, assignee, priority, story points, sprints, and other common reporting fields. You can:
- Apply selections globally for all in-scope projects
- Override per project when teams need different columns
Adding a field later automatically queues a backfill so existing issues gain the new column. No manual re-export is required.
Field selector tab → Global defaults → Save
Field selector tab → Project overrides → Select project → Adjust → Save
Supported field types
Most standard and custom Jira field types map to Fabric columns. Unsupported or computed fields are skipped during sync.
| Field type | Mirrored | | --- | --- | | Text, number, date, select | Yes | | User, version, component | Yes | | Rich text | Stored as text (formatting stripped) | | Transient / computed | No |
TODO: Publish full field-type matrix once schema is frozen.
Project scope
By default every project is exported. Switch to an include or exclude list to keep sandboxes and archived projects out of your dataset.
Removing a project from scope:
- Stops new exports for that project
- Cancels queued backfill work for it
- Does not automatically delete existing rows in Fabric (manual cleanup if needed)
JSM entities
When Jira Service Management is licensed, enable JSM tables for SLA cycles, request types, and approvals. See Features → JSM service data for limits.