Skip to main content
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.

​
Status mapping

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

​
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. New connections start with Read on for issues and Send worklogs off.

​
Synced records

Every synced record shows the Jira marker, “Last synced ” 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.