Jira
Ingests Atlassian Jira projects, issues, comments, and attachments — multi-resource (multi-site) cloud sites supported per user.
variant=info text="Issue tracking" variant=success text="OAuth" variant=success text="Maps ACLs"
What gets ingested
| Element | Mapped to |
|---|---|
| Project | _IssueProject |
| Issue (incl. sub-tasks, epics) | _Issue |
| Comment | _Comment |
| Attachment | _FileEntry + _Blob |
| Reporter, assignee, lead | _IssueUser / _Contact |
Authentication
- Type: Atlassian OAuth 2.0 (per-user). Multi-resource: a single user can connect more than one Jira Cloud site, each with its own delta cursor.
Access control mapping
- Project / issue restrictions configured in Jira are read through Atlassian's permissions API and mapped onto access groups via
AddPermissionToItem.
Sync cadence
- Default cron: every 15 minutes.
- Incremental sync: Jira's
updated >= <ts>JQL plus a watermark per project. Comments and attachments are fetched alongside their parent issue.
Notable
- Built on a shared Atlassian client (
AtlassianShared.cs) that the Confluence integration also uses, so OAuth refresh is consistent across the two. - Project-lead and reporter fields are linked into the same
_IssueUsernodes used by GitHub — so a query like "every issue assigned to alice@example.com in the last 30 days" spans both sources.