Open GoogleCodeExporter opened 8 years ago
I thought the same, so I would like to reinforce this issue. The task-time
could hide tasks closed by day.
Original comment by winsto...@gmail.com
on 1 Mar 2013 at 2:34
This is exactly what I am looking for as well. I use simple-task-timer to track
my daily time management. This program allows me to quantify my daily
productivity. As of now, the time for the tasks is cumulative and hence does
not allow me to see the time I spent on the tasks for that particular day. My
tasks are mainly
-work
-excess (play/lazing around)
-essential (eating/taking a shower)
-social
-sleep
-personal development/learning
As of now, the calendar only allows us to see the breakdown of the time spent
on individual tasks by date. I really hope to that there could be be an upgrade
where I can see a daily breakdown which shows me all the tasks that I have done
for the day. (think being able to see the exact same interface on the home
screen, except that "time spent" only accounts for the time spent on the
particular tasks on that particular day.
Thank you very much!
Original comment by LesterS...@gmail.com
on 16 Mar 2013 at 1:20
This would greatly improve the usability! A weekly breakdown would be great!
Original comment by john.wes...@gmail.com
on 5 Aug 2014 at 1:08
I would add to that, for those individual tasks repeated daily or several times
a day, the ability to calculate average time spent per instance, or per day (if
doing a cumulative time for a larger task or category.) (like how much time am
I spending each day or week just day dreaming, or working billable hours for
project x...cumulative. OR how much time am I spending on each inbound call or
outbound call, on average, how much time am I spending on after call work per
instance, how much time does it take for each invoice to pay, how many inbound
calls did I take? etc.
Ideally one could collect that data over time in the app, but I"m new with
this, and from the comments, looks like it is only one day at a time that is
kept.
THANKS!!
Original comment by KathyC...@gmail.com
on 30 Nov 2014 at 11:25
Original issue reported on code.google.com by
bmh1...@gmail.com
on 12 Sep 2012 at 2:08