TempoConnect the Jira projects that matter
Authorize Tempo through Jira Cloud, discover the projects available to the integration, and enable the projects you want to measure. Incremental syncs use issue update timestamps to keep the dataset current.
Issue and workflow metadata
Tempo stores normalized issue metadata and the status changes required to calculate time in the workflow. Jira status categories are resolved per project so custom workflows can map into consistent states.
- Issue key, title, type, labels, points, priority, and timestamps.
- Assignee, reporter, project, parent, and epic relationships.
- Current status and historical status transitions.
- Project statuses and shared issue types.
Work-health metrics from Jira
Issue cycle time begins when work first enters an in-progress state and ends at resolution. Lead time begins at issue creation. Throughput counts resolved work in the selected period.
- Cycle time and lead time.
- Throughput and bug ratio.
- Current WIP, WIP age, and stale issues.
- Epic progress, child issues, and scope movement.
Link planning data to pull requests
When pull-request branches, titles, or descriptions contain Jira issue keys, Tempo can link code delivery with the originating work item. This connects planning flow with PR and deployment outcomes without copying source code.