Link engagements to Jira projects so logged time flows in without double entry.
The Jira connection exists to solve one specific problem: your engineers already log time in Jira, and asking them to log it a second time in a separate timesheet is how time data goes bad.
Once connected, you link a Synthelio engagement to a Jira project, the issues in that project become timesheet codes in Synthelio, and the time your team logs against those issues in Jira flows through into their Synthelio timesheets. Nobody enters anything twice.
Every number in the P&L module is downstream of whether people log their time accurately. That is not a reporting problem, it is a data collection problem, and it is decided by how much friction sits between finishing a task and recording it.
A developer who logs work in Jira as they close tickets is recording time against the thing they just did, while they remember it. The same developer filling in a separate timesheet on Friday afternoon is reconstructing a week from memory, and the reconstruction will be rounded, tidy, and wrong. Non-billable time in particular tends to vanish in that process, which is exactly the time that explains why an engagement is losing money.
Removing the second entry step is worth more to your margin accuracy than any amount of reporting sophistication.
The integration works with Jira Cloud. Server and Data Center instances are not supported.
You need three things. Your Jira domain, which is just the subdomain from your Jira URL, entered without the https prefix or the atlassian.net suffix. The email address associated with your Jira account. And an API token, which you create in your Atlassian account settings.
Enter all three, then use Test Connection before turning the sync on. The settings panel shows when the sync last ran.
One thing to plan for: an Atlassian API token belongs to a person, not to your company, and the sync inherits that person's Jira permissions. If you generate the token from an account that cannot see every relevant project, the sync will not see them either. Worse, if that person leaves and their Atlassian account is deactivated, the token dies with it. Use an account that will outlast any individual's tenure.
The connection between the two systems is made at the engagement level. A Synthelio engagement is linked to a Jira project, and that link is what tells Synthelio which issues and which worklogs belong to which piece of client work.
Until an engagement is linked, nothing from Jira reaches it. If time is being logged in Jira and not appearing in Synthelio timesheets, an unlinked engagement is the first thing to check.
Issues from the linked Jira project become timesheet codes in Synthelio. That means time is attributed at the level your team already works at: a ticket, an epic, a specific piece of work, rather than a generic bucket.
This is a meaningful upgrade over the usual approach. When timesheet codes are coarse, everything lands in something like Development, and at the end of the engagement you know how many hours were spent and nothing at all about where they went. When codes come from real issues, an overrun has an explanation attached to it.
Time logged against those issues in Jira syncs into Synthelio, where it feeds timesheets, utilization, cost, and engagement margin like any other logged time.
Two habits are worth establishing with the team:
Jira covers delivery work. It does not cover everything a person's week contains. Time off, internal work, sales support, and anything that is not a ticket in a linked project still belongs in Synthelio directly.
Timesheet submission and approval also stay in Synthelio. Jira supplies the hours, but the monthly close, the submission state, and the approval workflow are Synthelio's job.
Does Synthelio write anything back to Jira? No. The sync reads projects, issues, and worklogs.
Can I use this with Jira Server or Data Center? No. Jira Cloud only.
What if someone corrects a worklog in Jira after logging it? Corrections belong in Jira, since that is the source. Do not fix the number on the Synthelio side and leave the two disagreeing.
Do we have to link every engagement to a Jira project? No. Link the ones your team actually tracks in Jira. Engagements without a Jira project work exactly as they did before, with time entered directly.
Tell us what you need. We will point you to the answer or write the article.
