Everhour adds issue-level timers and manual entries inside Linear so project hours stay tied to the work.
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.
A clean record should answer a practical review question: the issue that produced the work, the person who did it, the work date, and the duration. Useful entries stay close to the issue so the detail remains available when a manager reviews delivery time by Linear workspace, project, issue, status, or tag.
The same rule applies across individual and team work: log the time where the issue work happens. A short entry still needs enough context for a reviewer to accept the duration without reconstructing the week from memory. The goal is a record that supports per-issue totals, weekly review, and later billing or payroll handoff.
Project billing status belongs at the project level. Everhour projects can be set up as hourly project rate, hourly member rate, fixed fee, or non-billable, depending on the billing model. That setting controls how tracked time contributes to billing and reporting after people record hours against Linear work.
Task-level non-billable controls handle exceptions inside a billable project. Use them when a specific task should stay visible in reports but stay out of billable totals, such as internal coordination, rework, or research the client should not be charged for. The time entry records the work; the project and task billing setup determines how that work is treated.
A timer fits active work because it records duration as the session unfolds. Use it for focused implementation, review, QA, support investigation, or any task that breaks into multiple starts and stops. The resulting entry preserves the link to the issue that was open when the work happened and reduces cleanup during daily review.
Manual entry fits work recorded after the fact. Use it for meetings tied to an issue, offline work, pair sessions, and corrections to a timer that was stopped late or started on the wrong issue. Manual time still needs the same issue link, work date, duration, project context, and note when the entry needs explanation.
A single-entry tool is enough for a one-off note, a quick invoice backup, or a small project with one person entering time. The limit appears when several people log against the same Linear project and the record needs review before money or payroll decisions. At that point, time entries need submission status, manager decisions, locked periods, and a stable archive.
Everhour turns Linear issue entries into a managed review path. Everhour Timesheets support weekly project hours or working hours for review, depending on whether the team tracks task time, timecards, or both. Managers can approve, reject, or partially approve submitted time before billing or payroll review, and approved time stays protected for regular members.
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.
A useful record includes the Linear issue, project, work date, duration, person, and a note when context affects review. Billing treatment is configured separately at the project level, with task-level non-billable controls where applicable. Complete records support project review, invoice backup, and weekly timesheet approval.
Use a timer for live work with uncertain length, especially development, QA, investigation, and review. Use manual entry for work recorded after the fact, such as a meeting tied to an issue or a correction to a stopped-late timer. Both methods should link tracked time to the relevant Linear issue.
Linear issue estimates describe effort or complexity for planning. Logged hours record time actually spent. Keep the two fields separate, then compare reported time with the estimate during review to find oversized issues, under-scoped work, or tasks that need clearer breakdown before the next cycle.
Generic project-level logging damages the report because the hours lose their issue context. Split delivery work by issue, keep task notes clear, and handle billing treatment through the project and task setup. Large undivided blocks make per-issue totals unusable during project review.
One entry should cover one issue when the work produces issue-level output. Split a 3 hour work block across the issues that consumed the time, even when they belong to the same project. Shared meetings or general triage can use a broader entry if the team's review policy allows it.
Everhour Timesheets support weekly Linear project hours or working hours for review, depending on whether the team tracks task time, timecards, or both. Team members submit time for review, and admins can approve, reject, partially approve, or lock entries before payroll or billing teams use the totals as final records.
Everhour reporting can use Linear workspace, project, issue, status, and tag data when reviewing tracked time. Managers can group and filter entries by available project context, member, client, and date range, then export reports for spreadsheet work or client backup.
Use Everhour Timesheets to collect weekly Linear project hours or working hours, depending on the team's tracking setup, then route submissions for approval and lock approved entries before billing or payroll review.
14-day free trial · No credit card · Cancel anytime
