> ## Documentation Index
> Fetch the complete documentation index at: https://usepike.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> How to connect Jira Cloud to Pike, sync Jira issues into Pike tasks, map statuses, and send Pike time to Jira as worklogs.

The Jira integration syncs Jira issues into Pike tasks in real time and, when you turn it on, sends time logged in Pike to Jira as worklogs. Developers stay in Jira, while delivery leads see hours, budget burn, and margin on the same work in Pike. It works with Atlassian Cloud sites.

## Connect Jira

1. Go to **Workspace settings** → **Integrations** → **Jira**.
2. Click **Add integration**.
3. Authorize Pike for your Atlassian Cloud site in the popup.
4. On the integration page, map each Jira project, or a saved JQL filter, to one Pike project.

Only workspace admins can connect or disconnect Jira.

### Connect your personal account

Sending worklogs posts time as the member who logged it, so each member who logs time on synced tasks connects their own Jira account.

1. Go to **Settings** → **Connections**.
2. Connect your Jira account and follow the prompts.

## Import data

On the integration page, click **Import data**. The stepper runs entities in dependency order, so epics import as phases before the issues that sit in them. It skips entities whose **Read** toggle is off, names them, and links to sync settings.

## What syncs

Jira issues become Pike tasks.

| Jira | Pike | Notes |
| - | - | - |
| Summary | Task title | |
| Description | Task description | |
| Issue type and labels | Labels | |
| Assignee | Assignee | Matched by email |
| Due date | Due date | |
| Original estimate | Hours allocated on the assignee | |
| Epic or parent | Phase | When **Map epics to phases** is on |
| Status | Task status | Through the status mapping table |
| Worklog | Time entry on a synced task | Pike to Jira, when **Send worklogs** is on |

### Status mapping

Admins edit the status mapping table on the integration page. Defaults:

| Jira status | Pike task status |
| - | - |
| To Do | To Do |
| In Progress | In Progress |
| In Review | In Review |
| Done | Done |

### Worklogs

With **Send worklogs** on, time logged in Pike on a synced task posts to Jira as a worklog with the duration, date, and comment, as the member who logged it. Editing or deleting the Pike time entry updates or deletes the worklog. Each member needs their personal Jira connection.

### Source of truth

Once a record is linked, Jira owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten. Jira owns all issue fields. Pike owns time entries, billable status, rates, and allocations.

### Schedule

Changes in Jira reach Pike in real time through Jira webhooks. **Import data** and **Refresh** always run on demand.

## Sync settings

While Jira is connected, the **What syncs with Jira** card sits under the top button row on the integration page. Each entity has a **Read** toggle (Jira to Pike) and, where supported, a **Send** toggle (Pike to Jira). Toggles save immediately.

| Entity | Read | Send |
| - | - | - |
| Issues | Yes | Not available |
| Worklogs | Not available | Yes, off by default |

New connections start with **Read** on for issues and **Send worklogs** off.

## Synced records

Every synced record shows the Jira marker, "Last synced {time}" or "Not synced yet", and a **Refresh** action. **Refresh** shows only while **Read** is on for that entity.

Each synced task also shows the Jira issue key and an **Open in Jira** link.

### Sync issues

Records that fail to sync appear in the **Sync issues** list on the integration page, with the record, the reason, and a **Retry** action. The integration never deletes Pike data on its own. A record removed in Jira is marked "Removed in Jira" in Pike, never deleted.

## Disconnect

Disconnecting Jira stops syncing and keeps all imported data. Linked records keep their history.

## Permissions

Synced data respects Pike roles and private projects. A private project's tasks never sync out to anyone who cannot see the project in Pike.

## Limits

* Pike does not create Jira issues.
* Jira custom fields do not sync, except original estimate.
* Jira Server and Data Center are not supported. The integration works with Jira Cloud only.

## Related

* [Jira integration overview](https://usepike.com/integrations/jira): What syncs, how agencies use it, and FAQs.
* [Linear](https://usepike.com/docs/integrations/linear.md): Sync Linear issues into Pike tasks.
* [Azure DevOps](https://usepike.com/docs/integrations/azure-devops.md): Sync work items and send completed work.
* [Project time](https://usepike.com/docs/project/project-time.md): How time on a project adds up.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.