Closed taskwarrior closed 6 years ago
Migrated metadata:
Created: 2014-02-21T15:44:48Z
Modified: 2015-04-07T04:06:05Z
Paul Beckingham on 2014-04-16T03:40:04Z says:
Needs for time tracking (from years of arguing about this):
Adam Coddington on 2014-04-16T05:40:06Z says:
I'm not sure if my opinion matters on this -- I'm not likely to use taskwarriior for time tracking, really, so I have no horse in this race -- but having spent a significant chunk of time writing time tracking software, it seems like the time tracking (via start
and stop
) functionality we already have is already at the cusp of being useful, and that we may be overcomplicating things by dealing with holidays, workweek boundaries, moon phases, and the star sign compatibility preferences of the user.
It seems to me like the core issues we currently face w/r/t using taskwarrior for timetracking are simply:
task start
and task stop
/task done
executions.Paul Beckingham on 2014-07-02T00:37:12Z says:
I think the new tasksh project is the ideal place to implement time tracking. The shell implements its own commands, stores its own data, and runs for more than milliseconds at a time.
Paul Beckingham on 2015-04-07T04:06:05Z says:
While this issue is closing, the linked issues are unaffected.
Renato Alves on 2014-02-21T15:44:48Z says:
We are currently in the process of redesigning the time tracking functionality in taskwarrior.
Since several issues exist already related with time tracking, this issue will serve as a hub to connect and collect all the use cases reported by users as well as the place for progress report.