Turn Jira worklogs into HR-ready, locked period reports. Overtime, shortfall and recuperation balances per technician — exportable, auditable, and ready to hand off to any HR or payroll system.
From raw Jira worklogs to a clean, locked, auditable handoff — without spreadsheets.
Your technicians already log time in Jira. Worktime turns those worklogs into the period reports HR and payroll actually need — worked versus expected hours, overtime, shortfall and recuperation balances — then locks each period with an audit trail so the numbers stop moving once they're signed off.
Worked, expected, overtime and shortfall per technician across monthly, weekly or custom periods — the numbers payroll needs, already reconciled.
Optional review step — submit a period for approval, with approve / reject and reasons captured, before it locks. Skip it entirely for one-person teams.
XLSX and CSV exports laid out for handoff — drop them straight into your HR or payroll process.
Pull the same period data programmatically for direct integration with any downstream HR system.
A per-technician daily record — first-in, last-out, break and net worked time — for statutory working-time recordkeeping. Exported as CSV or an Excel sheet. Recordkeeping support, not legal advice.
Re-reads Jira and flags any worklog added, edited or deleted since a period was locked — so you can show a signed-off period still matches the source.
Locking freezes the period to an immutable snapshot; every lock, unlock and markup edit is recorded with who did it and when.
Each report captures the worklogs, rules and engine version it was built from — so last month's numbers reproduce exactly, every time.
Each technician sees their worked and expected hours for the current period — no admin access required.
A running view of accrued overtime and recuperation taken, so there's no end-of-month surprise.
Once a period is locked, technicians see exactly what was signed off for them — no black box.
Per-technician hour expectations — no JSON, no scripts. Just the contracted hours each person is measured against.
Define shift patterns and rotations so expected hours reflect how your team actually works.
Maintain holidays per region, with one-click national import so you don't enter them by hand.
Set how overtime accrues and how recuperation is drawn down — the rules calculate balances for you.
Enter HR-managed absences — sick, vacation, training — so expected hours adjust correctly without leaving Jira.
The default. Zero configuration — Worktime reads the worklogs already in Jira.
Already tracking time in one of these? Use it as a drop-in alternative source instead of native worklogs.
Third-party sources use your own API key per installation — customer-owned, never shared with 3T Apps.
All data stored in Forge KVS — Atlassian's own infrastructure, in your configured data residency region.
No third-party backend. Worktime computes from your Jira worklogs and stores results in Atlassian storage.
Source-adapter egress (Tempo / Clockwork / eazyBI) and holiday import fire only when you enable them. View security page →
Free for up to 10 users. Coming soon to the Atlassian Marketplace.