Reconnecting…
Waiting for the connection. It is taking a while. Reload the page
This page hit a problem
It is reconnecting and will carry on from where it was.
Time and invoicing
A helpdesk request, a project ticket and an afternoon of free-form work are all tracked in one place, against the customer's contract. The same hours show what a project or a feature really took and cost, whether the customer's service levels were kept, and what to invoice. Not a time tracker bolted onto a ticketing system: one product, one set of data, everything included.
An activity is one row wherever it was spent. Start the clock from a ticket's page or type a line on the activities page; label it with a ticket's key and it is the ticket's logged time, the customer's hour and the invoice's line at once.
Answer a customer's request and log the time on it. The request's project is billed to the customer, so the hour lands on their contract.
In the guide →Work a story from the board, log against its estimate, and see the epic add up what its stories and sub-tasks took.
In the guide →A description, labels and a project, or nothing but the description. The start defaults to the end of your last activity; an end before the start is the next day.
In the guide →Set the rate on the customer's contract, group the work into phases with a budget of days, and generate the invoice from the hours: a PDF shown as it will print, edited before you download it, with tax and a breakdown by label category. Nothing is stored; the invoice is worked out from the hours each time, and the hours you have invoiced can be locked.
Track your time
On tickets, on projects or free-form, with labels that autocomplete from your recent work.
Set the contract
A rate and a currency per customer, a reference and the description printed on the lines; each customer's contract carries its own currency.
Define the phases
Billing periods with a date range, an optional rate override and a budget of working days.
Generate the invoice
Pick the phases, or a period's hours by project, epic or category, and download the PDF.
This is what a time tracker on its own cannot say, because it does not know the tickets.
Nothing here is an extra. Every workspace has all of it, hosted or on your own servers, at one price per seat, and the people who raise requests are never a seat.
Working in a customer's Jira as well as your own workspace? Label your activities with their issue keys and get the time across without plugins or API tokens.
Copy a ready-made script from the reports page and paste it into the browser console while their Jira is open: your entries become worklogs under your own session.
In the guide →A second script posts your activity notes as comments, one per activity with a note, so the context lands on the ticket.
In the guide →On Jira Server or Data Center with Tempo, download a CSV aggregated by issue key and day, ready for import.
In the guide →Coming the other way, the Jira import brings every worklog in as an activity on its ticket, with Tempo's attributes and accounts kept. A ticket URL prefix on the customer turns labels into links in the HTML exports.
Log the hours as you work, keep customers and projects in order, and turn the month's time into a PDF invoice.
Contracts with different rates and currencies, phases that respect a budget of days, and your worklogs pushed to the customer's Jira in seconds.
Give colleagues a role on the customer and see everyone's time side by side, with the cost of it for those who may see the money.
The time on a request is on the customer's contract, and the contract's service levels tell you which request to work next.
An Elastic Time account comes across whole from its export: people, customers, contracts, phases, label categories and every activity with its lock. Toggl Track's export imports with nothing to map; Clockify, Harvest, Timely or any CSV of entries with the columns mapped on screen, the time zone chosen, and duplicates skipped. Jira's worklogs arrive with a Jira backup.
A workspace takes a couple of minutes and asks for no card. An installation is one container image and a compose file.