Tempo

Tempo

Tempo for Jira tracks time through worklogs. Accounts, customers, and workload schemes organize billing and capacity. The Cloud REST API authenticates with a Tempo private API token sent as Authorization: Bearer; this bundle path is token-based only (no OAuth connect).

Data model

• Worklogs — time entries linked to Jira issues.
• Accounts — Tempo accounts (often map to Jira projects or billing).
• Customers — clients for billing.
• Workload schemes — capacity and allocation rules.

Gotchas

• Jira coupling: worklogs reference Jira issue keys; Tempo must be installed on the same Jira site.
• Token expiry: Expired or revoked tokens return 401 — auth failure after a long quiet period usually means the Tempo API token needs renewal on the Jira site.
• Pagination: accounts/customers/workload schemes/worklogs accept offset + limit.
• Worklog windows: Bound worklog listing with from_date / to_date (or updated_from) — unbounded lists are slow and often too large.
• OAuth vs private token: Tempo also ships OAuth 2.0 apps for multi-user integrations; this bundle exposes the private-token path only.