Work estimation without story points using T-shirt sizes as a custom field, time estimates vs actuals via tracking and throughput counting. No Fibonacci debate.
All
Project management
Estimation
Custom fields
Time tracking
Workflow
Software development
Self-hosted
Source available
Licensing
Security
Custom statuses
Github
Issue tracking
Sqlite
Data ownership
Comparison
Jira alternative
Kanban
Docker
Custom issue types
Release planning
Timeline
Labels
Adoption
Capacity planning
Agency
Retainers
Project groups
Pricing
Scope creep
Board view
Multiple views
Pro edition
Project views
Board
Grid
Release
Ui/ux
Design
Sso login
Oidc
Sso providers
Grid view
Team collaboration
Vision
Project planning
Eigenfocus
Focus
Values
Why teams stop tracking time comes down to three friction points: context switching, manual entry and no visible payoff. Built-in tracking fixes all three.
Time tracking workflow visibility helps non-billing teams spot time sinks, understand which phases eat hours and make capacity decisions based on data.
Use per-project time tracking with project groups to track retainer hours. Set up a project per retainer period, log hours and review totals via time reports.
Scope creep shows up as a slow drift between estimated and tracked hours. Compare time logged per deliverable against estimates weekly to spot overruns early.
Bad estimates come from guessing. Review historical hours per issue type, build baseline ranges and adjust for scope. A time tracking project estimation method.
Time tracking alerts, flexible manual entry, easier issue completion, global issue URLs and improved draft saving.