Connect Jira to EngLedger
Authorise EngLedger with Jira OAuth, choose projects to sync and understand what ticket, worklog and sprint data is imported, read-only.
Updated 12 July 2026
EngLedger connects to Jira Cloud with OAuth 2.0, requesting read-only access
to work items and users (read:jira-work, read:jira-user) plus offline
access so it can refresh tokens in the background. EngLedger never writes to
your Jira.
Authorise Jira
Open Integrations in EngLedger and choose Connect on the Jira Cloud card. You're redirected to Atlassian's consent screen.
Review the requested access and approve. You're returned to EngLedger's project selection screen with the connection confirmed.
Choose projects
Every project the connected account can see is selected by default. Remove any you don't want synced. Projects are listed with their name and key. Saving the selection starts the first sync; the first pass backfills history so it takes longer than the routine incremental syncs that follow.
What gets synced
From each selected project, EngLedger imports:
| Entity | Used for |
|---|---|
| Projects | Grouping and filtering reports |
| Tickets | The unit that classification, linking and effort attach to |
| Worklogs | Logged time: the basis of worklog-derived effort |
| Sprints | Sprint context on tickets |
| Status transitions | Cycle time reporting |
Ticket assignees, reporters, worklog authors and status-change authors are recorded as provider identities. Link them to people so logged time is attributed to the right person. Identities with a matching email are linked automatically (see People and identities).
Worklogs are the raw Jira records; EngLedger derives its effort ledger from them without modifying anything in Jira. How that derivation works (and what the resulting numbers do and don't tell you) is covered in the effort model.
Token expiry and reauthorisation
Access tokens are refreshed automatically in the background. If a refresh fails because the grant has expired or been revoked, EngLedger stops syncing and marks the integration Needs reauth on the Integrations page rather than retrying silently. Run the Connect flow again to reauthorise. Your project selection is preserved.
Sync cadence
Scheduled sync runs every 30 minutes by default. Jira Cloud does not publish a fixed hourly request ceiling the way GitHub and Bitbucket do; EngLedger still tracks its API usage and backs off when Atlassian signals pressure.
Disconnecting
Disconnect pauses the integration; synced data is retained and syncing stops. Reconnect at any time with the same flow.
Next steps
- Understand how worklogs become effort
- Pair Jira with a code host: Connect GitHub or Connect Bitbucket
- Everything EngLedger integrates with