# Jira and Jira Tempo integration

> Connect Jira to Workload: Tempo time logs, read-only import of projects and epics, capacity summary posted back to Jira. Setup steps and FAQ.

- HTML: https://www.simpleworkload.com/en/integrations/jira
- Markdown: https://www.simpleworkload.com/en/integrations/jira.md

## How do you connect Jira to Workload?

Workload connects to Jira in two complementary ways. Time logged in Jira Tempo is synced with a Tempo API token to feed planned vs actual. Jira projects and epics are imported read-only through the Jira integration, with an optional capacity summary posted as a comment. Neither modifies your existing tickets.

Available from the Professional plan. The Tempo token is set up under Settings > Timesheet integrations.

## What gets synced

- Jira Tempo → Workload: worklogs (date, hours, description, project, author) for planned vs actual
- Jira → Workload: projects, epics, and dependencies, read-only
- Workload → Jira (optional): a planned-capacity summary posted as a comment on the first issue of the mapped project

## Prerequisites

- A Workload account on the Professional plan or above
- A Tempo API token (for time) and, for the Jira integration, an Atlassian API token tied to your email, or an OAuth connection
- On the Jira side: “Browse projects” permission and, for the optional posting, “Add comments”

## Step-by-step setup

1. In Workload, open Settings > Timesheet integrations and choose Jira Tempo.
2. In Tempo, open Settings > Data Access > API Integration, click New Token (validity of your choice, read access to worklogs), then paste the token into the wizard and validate the connection.
3. Run a first sync: worklogs arrive in Workload.
4. Match Tempo projects to your Workload projects. Automatic matching is based on name similarity; you can correct it by hand.
5. To import projects and epics, open Settings > Integrations, add Jira, and test the connection.
6. Map Jira projects to Workload projects, then run the sync (read-only).
7. Optional: enable allocation posting to Jira to publish the weekly capacity summary.

## Good to know

- Timesheet integrations sync automatically every 4 hours, or on demand from the integration page.
- A project mapping confirmed by hand is never overwritten by automatic matching.
- A Tempo token expires (30 days by default): pick a suitable validity or renew it, otherwise the integration goes into error.
- Posting to Jira is one-way: Workload writes a comment and never changes your ticket fields.
- Entries without a mapped project are still imported but unattached: complete the mapping.
- Tempo only provides the author's Atlassian account ID. To attach time to a member, Workload looks up the author's name and email through the organization's Jira integration (if active), then matches a member by email or exact name. Without a Jira integration, or if the user hides their email and the name does not match, the time stays attached to the project but not to a member.

## Frequently asked questions

### Do you need Jira to use Workload?

No. Workload runs standalone with CSV import. Jira and Tempo are optional integrations, available from the Professional plan.

### Does Workload change my Jira tickets?

No. Projects and epics are imported read-only. The only optional write is a capacity summary comment on the first issue of the mapped project.

### How often is Tempo time refreshed?

Every 4 hours for active integrations, and on demand with manual sync.

### What if a Tempo project does not exist in Workload?

The entry is imported without a mapped project. You can then create the project or fix the mapping; automatic matching proposes a project with a similar name.

### How do I compare planned and actual?

Once time is synced and attached to projects, planned vs actual appears in reports and the committee pack.

## Sitemap

- [Markdown sitemap](https://www.simpleworkload.com/sitemap.md)
- [XML sitemap](https://www.simpleworkload.com/sitemap.xml)
- [llms.txt](https://www.simpleworkload.com/llms.txt)
- [llms-full.txt](https://www.simpleworkload.com/llms-full.txt)