JIRA + Go Fig
Integrate JIRA project data with Go Fig for R&D visibility and resource allocation insights.
JIRA tracks what engineering is working on, but connecting that to financial outcomes is hard. Go Fig pulls JIRA issues, sprints, and time tracking into your financial platform. See project costs in real-time, track R&D capitalization, and understand where engineering investment is going.
Key facts
- Deployments supported
- Cloud, Server, Data Center
- Sync cadence
- Hourly incremental
- Custom fields
- Fully supported
- Auth
- OAuth 2.0 or API token
What you can do with JIRA data in Go Fig
Project Cost Tracking
Track actual costs by project, epic, or initiative using JIRA time data.
Resource Utilization
Understand engineering capacity and allocation across projects.
R&D Capitalization
Identify and track capitalizable work with JIRA issue classification.
Data available from JIRA
Go Fig extracts and normalizes the following data from your JIRA account:
How to connect JIRA
Connect your Jira site
Install the Go Fig app from the Atlassian Marketplace. Cloud users authenticate via Atlassian OAuth and select sites; Server / Data Center users provide a base URL and API token.
Pick projects and custom fields
Most R&D-capitalization use cases need a few specific custom fields (e.g., a 'Capex' or 'Initiative' picklist). Select the projects in scope and the custom fields that carry capitalization, billable, or cost-center metadata.
Define your engineering cost model
Bring in headcount cost from your HRIS or payroll connector and Go Fig will suggest a fully-loaded cost-per-engineer-hour. This becomes the multiplier when joining worklog hours back to financial cost.
Build the R&D capitalization report
A starter flow joins worklog hours × loaded rate × capitalization-eligible-flag and emits a journal entry friendly summary by month, project, and GL account. Most controllers wire this into their close checklist.
Authentication: OAuth 2.0 via Atlassian. Connection is scoped to specific Jira sites (cloud) or to an API token (self-hosted). Read-only by default, no write permissions are requested.
Common Questions About JIRA Integration
Does Go Fig support Jira Cloud, Server, and Data Center?
Yes to all three. Cloud uses OAuth 2.0; Server and Data Center use a personal API token with a self-managed base URL. The data model and downstream flows are identical regardless of deployment type.
Can I track R&D capitalization automatically with Jira data?
Yes, this is one of the most common Jira use cases. By tagging epics or issues with a capitalization-eligible flag (custom field, label, or component) and joining worklog hours to a per-engineer loaded cost rate, Go Fig produces a defensible capex-vs-opex split that ties back to specific Jira tickets, which is what auditors typically ask for.
What about engineers who don't log time in Jira?
Most engineering orgs don't track time at the worklog level. In that case, allocate engineer-time using assignee × sprint membership × story-points-completed, all of which Jira does capture. Go Fig has a pattern flow for this and the resulting allocations correlate well (within 5–10%) to organizations that do log time.
Can Go Fig combine Jira data with GitHub or GitLab activity?
Yes. Jira issue keys are typically referenced in commit messages and PR titles. Go Fig joins on issue key to attribute commit and PR throughput back to the same Jira issue, sprint, or epic, which gives a cleaner picture of effort than time tracking alone.
How current is the Jira data inside Go Fig?
Hourly incremental sync by default, anchored on issue updated timestamp. Full reindex runs nightly. For close-week dashboards, Celeste can also trigger an on-demand sync of a specific project to ensure the most recent worklogs are reflected.
Related Engineering integrations
Other systems Go Fig connects into the Financial Intelligence Graph, often alongside JIRA.
Industries running JIRA with Go Fig
Strategic CFOs in these industries typically stitch JIRA into their Financial Intelligence Graph alongside their ERP and operational systems.