Timesheets people actually fill in.
A weekly grid you can drive from the keyboard, a timer that survives a page reload, billable flags and approvals — all written as ordinary Jira worklogs, so nothing is locked into the app.
The real module, running right here.
Working software on sample data — the same interface that renders inside Jira. It plays a short tour when it comes into view; click anywhere in it to take over.
Type into any cell — 2h, 1.5, 90m and 1h30 all parse. Start the timer, mark work billable, then submit the week for approval.
Built for the job, not the brochure.
Keyboard-first weekly grid
Type 2h, 1.5, 90m or 1h30 into any cell and it parses, and every entry becomes a real Jira worklog.
A timer that survives a reload
Start it on an issue, close the tab, come back later — it is still running, and stopping it logs the time.
Billable, accounts and categories
Mark work billable or not, charge it to an account and give it a work category, the fields billing and reporting depend on.
Approvals and locked periods
People submit a week; approvers approve or reject it. Past periods can be locked so the numbers that went to finance stay put.
Schedules, holidays and capacity
Working schedules and holidays set what a full week looks like, so utilisation compares hours with what was actually available.
Rates, utilisation, invoicing
Rates turn hours into money, utilisation shows who is stretched, and exports feed the invoice.
Three steps from install to answer.
Log time your way
Type into the grid, start the timer, or keep logging in Jira as you do today — it is all the same worklog.
Submit the week
People submit; approvers see the people they approve and approve or reject the week.
Report and bill
Hours flow into charts, budgets and invoicing exports with their billable flags and accounts.
Inside Atlassian, with Jira’s rules.
A timesheet says who worked, for how long, on whose account. That is personal data, so it stays inside Atlassian’s boundary, and hours follow their own visibility rule on top of Jira’s project permissions. What “never leaves your instance” means →
- You see your own hours
- Project admins see hours in their projects
- Approvers see the people they approve; hours on issues they can’t open show as one anonymous line
- Jira admins see everyone’s
Straight answers.
Can I move my existing Tempo history across?
Yes, on day one. Export your logged time from Tempo as a CSV and import it on the app’s admin page once the first sync of your worklogs has finished. Accounts, billable flags and work categories are matched onto the Jira worklogs Tempo created, and hours with no Jira worklog behind them are kept as read-only history. It works from the export rather than Tempo’s API, because calling Tempo’s servers would mean your data leaving Atlassian.
Can people see hours they shouldn’t?
Issue data is limited to the projects the viewer can browse, and hours follow their own rule: you see your own, project admins see hours in their projects, approvers see the people they approve, and Jira admins see everyone’s.
Is time stored somewhere other than Jira?
Hours are Jira worklogs. The app adds what Jira has no field for — billable flags, accounts, categories, approvals — in its own Forge storage, inside Atlassian.
Guides and articles.
Moving from Tempo Timesheets: what comes across, and how
Switching time-tracking apps is only possible if your history comes with you. Here is exactly what the import reads from a Tempo export, and what it does with each row.
Read the guide →Turn a support address into Jira issues with Cloudflare Email Routing
Forward a support address on your own domain into Jira, so each new message becomes an issue and each reply lands as a comment — without giving any app a mailbox.
Read the guide →See Claude Code spend per person, team and Jira issue
Point Claude Code’s own telemetry and a GitHub webhook at Workforce Intelligence, and see what AI coding costs — per person, per team, and per Jira issue it helped build.
Read the guide →Be first in when it opens.
One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.
Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.