How do you connect Jira to Workload?

In Workload, open Settings > Integrations, add Jira, and connect your Jira Cloud site with your Atlassian account (OAuth) or an API token. Workload then imports your projects, epics, and dependencies read-only, without changing your tickets. Sync of time logged in Jira Tempo is coming soon; until then, import it as CSV.

Jira Cloud integration

Import your Jira projects, epics, and dependencies read-only, and optionally publish planned capacity back to Jira.

Available from the Professional plan. Jira Tempo time sync is coming soon.

Last updated :

What gets synced

  • Jira → Workload: projects, epics, and dependencies, read-only
  • Workload → Jira (optional, with an API token): a planned-capacity summary posted as a comment on the first issue of the mapped project
  • Jira Tempo → Workload (actual time): coming soon. Until then, import your Tempo exports as CSV for planned vs actual

Prerequisites

  • A Workload account on the Professional plan or above
  • A Jira Cloud site and an Atlassian account with access to it (OAuth connection), or an Atlassian API token tied to your email
  • On the Jira side: “Browse projects” permission and, for the optional posting, “Add comments”

Step-by-step setup

  1. In Workload, open Settings > Integrations and add Jira.
  2. Sign in with your Atlassian account and grant read access. You can also enter your site URL, your email, and an Atlassian API token.
  3. If your account can access several Jira Cloud sites, pick the one to sync.
  4. Map your Jira projects to your Workload projects.
  5. Turn on epic import and, if needed, dependency import, then run a first sync.
  6. Optional, with an API-token connection: turn on allocation posting to publish the capacity summary in Jira.

Good to know

  • Projects, epics, and dependencies resync automatically about every 30 minutes, or on demand.
  • The OAuth connection is read-only. Posting allocations to Jira requires an API-token connection.
  • Posting is one-way: Workload writes a comment a few minutes after an allocation changes and never changes your ticket fields.
  • If access to the chosen Jira site is lost, sync pauses until you pick a site again.
  • The integration is built for Jira Cloud.
  • Time logged in Tempo is not synced yet: use CSV import in the meantime.

Frequently asked questions

Do you need Jira to use Workload?

No. Workload runs standalone with CSV import. The Jira integration is optional, available from the Professional plan.

Does Workload change my Jira tickets?

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

Is time logged in Jira Tempo synced?

Not yet: native Tempo sync is coming soon. Until then, export your Tempo worklogs as CSV and import them into Workload to compare planned and actual.

How often is Jira data refreshed?

About every 30 minutes for active integrations, and on demand with manual sync.

OAuth or API token: which should I pick?

OAuth is the simplest and is enough to import projects, epics, and dependencies. Pick an API token if you also want to post the capacity summary to Jira.

Go further

Connect your tools in minutes

Connect Jira or import your data as CSV to get started today. Time sync (Jira Tempo, Azure DevOps, Toggl, Clockify) is coming soon.

14-day free trial