Everhour adds issue-level timers to Linear work, so tracked hours stay tied to projects, issues, and budgets.
Try with my Linear
$10k of $15k
Hourly
0:00:00
Alejandro Luna0:00:00Kai Nani0:00:00Kai Nani0:00:00Click!
Dave Jung0:00:00Alejandro Luna0:00:00Dave JungThe calculator gives you the number — Everhour takes it from there.
One click and you're timing. Start a timer, add an entry, edit the details. This is exactly how it feels in Everhour.
Set a budget, assign rates, and get alerted before you're over.
Measurement
Track your budget through time or costs
Every report you need — configured your way, always up to date.
Tracked hours flow straight into a polished invoice — no copy-paste, no manual math.
This page is for recording live work against Linear issues without turning issue estimates into timesheets. Start the timer on the issue you are working on, stop it when the work ends, and keep the entry tied to the same issue, project, date, and person. The useful outcome is a clean record of time actually spent, not a second planning estimate.
A good timer habit creates reviewable entries as work happens. Each record should carry the issue, project, date, duration, billable flag, and a short note when the title alone does not explain the work. That gives a manager or client enough context to separate product work, support cleanup, research, bug fixes, and non-billable internal time.
A running timer fits focused work on one issue: coding a fix, testing a change, writing specs, or handling review comments. Start it when the task begins and stop it when context changes. That avoids end-of-day reconstruction and keeps the duration attached to the Linear issue that produced the work.
Manual time entry fits work recorded after the fact: a meeting tied to an issue, a short review finished away from the browser, or a correction after someone left a timer running. Manual entries still need the same fields as timer entries. Treat manual time as a completed record, not a loose note to clean up later.
Linear estimates describe effort or complexity. Linear supports Exponential 1/2/4/8/16, Fibonacci 1/2/3/5/8, Linear 1/2/3/4/5, and T-shirt XS/S/M/L/XL scales, plus optional extended values. Those estimate values support planning and issue-flow analytics; they are not logged clock time, labor cost, or billable hours.
This distinction matters when teams compare planned work with actual work. An issue estimated at 3 points can take 45 minutes or 6 hours. An unestimated issue can also carry a default value of 1 estimate point unless that behavior is disabled in estimate settings. Keep estimate points for planning and logged time for payroll, billing, budget review, and project analysis.
A free, one-off timer is enough when you need a personal note of how long one Linear issue took. It works for a quick check, a solo work session, or a rough handoff note. It stops being enough when several people log time, clients need billable detail, budgets have limits, or managers need approved weekly records.
Everhour turns Linear issue time into a managed workflow. It supports project budgets configured as hourly rate, fixed fee, or non-billable, with email alerts at 50%, 80%, or custom thresholds and auto-stop timers when a budget is exceeded. For ongoing work, approvals, locked periods, reporting, and billing handoff protect the record after time is logged.
This content is for general information only, may not be fully up to date, and is provided without any warranty or liability.
High Performer
G2
Summer 2026
Best Ease Of Use
Capterra
Summer 2026
Rated in the top time trackers across G2, Capterra, and TrustRadius — with consistent praise for ease of use, integrations, and support.
Yes. The useful setup records the timer entry against the Linear issue where the work happened, then carries that issue context into review and reporting. Keep one entry on one issue whenever possible. Splitting unrelated work across separate issue entries prevents mixed notes, inflated totals, and billing questions later.
Select the correct issue and confirm the work belongs to that project before starting the timer. After the session, check the duration, billable flag, and note. A short note matters when the issue title is broad, such as "API cleanup," because reviewers need to know which work the time entry covers.
Stop the timer when the work no longer belongs to the current Linear issue. A meeting, support interruption, or second issue needs its own entry if the time should be reviewed separately. Leaving one timer running across unrelated work creates a single duration that cannot be defended by issue, project, or billable status.
Estimate points describe effort or complexity for planning. Timed work records the clock duration spent by a person on an issue. Linear analytics use estimate values for effort-based measures, while time entries support timesheets, budgets, billing, and cost review. Treating points as hours creates wrong totals.
Correct the entry as soon as the mistake is found and add a note if the final duration needs explanation. A forgotten timer can overstate issue time, consume budget incorrectly, and distort weekly review. Teams should check active timers and unusual daily totals before approving time for billing or payroll use.
Everhour Project Budgeting tracks time and money budgets as people log time on Linear work. Teams can use hourly rate, fixed fee, or non-billable project settings, receive email alerts at 50%, 80%, or custom thresholds, and stop timers automatically when a budget is exceeded.
Everhour Timesheets collect project hours and working hours by person so managers can approve, reject, or partially approve submitted time. Submitted and approved time is protected from edits, which keeps Linear issue time ready for payroll, billing, and reporting review.
Track approved hours from Linear issues, compare them with project budgets, and keep budget alerts close to the work. Everhour turns live issue time into budget-ready records.
14-day free trial · No credit card · Cancel anytime
