Pike and
Jira
Sync Jira issues into Pike, and see hours, budget, and margin on the work.

At a glance
- Direction
- Jira to Pike in real time. Pike to Jira for worklogs.
- Who sets it up
- Admin connects the site. Members sending worklogs connect Jira.
- Source of truth
- Jira for issue fields. Pike for time, rates, and allocations.
- Plan
- All plans
- Documentation
- Jira docs
What syncs between Jira and Pike
| Jira | Pike | Notes |
|---|---|---|
| Summary and description | Task title and 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 |
Admins edit the status mapping table. Defaults map To Do, In Progress, In Review, and Done to matching Pike statuses.
Set up and use Jira
Connect
- 1.Go to Workspace settings → Integrations → Jira and authorize your Atlassian Cloud site.
- 2.Map each Jira project, or a saved JQL filter, to one Pike project.
- 3.To send worklogs, members connect Jira under Settings → Connections.
How to use it in your business
- Track budget burn on Jira work. Original estimates become allocated hours, so leads see planned against logged hours.
- Bill from the hours developers log. Pike hours carry billable status and reach Jira as worklogs, so nobody logs twice.
Limits
- Pike does not create Jira issues.
- Jira Server and Data Center are not supported.
Setup steps and field mappings: Jira docs.
Jira integration questions
See Pike and Jira working together on your data.
ISO 27001
GDPR
SOC 2 Type II
Built to keep sensitive client data secure and private.



