add duration estimation for activity
It would be nice to supplement task description with esimation of duration (say, in minutes) required for this task to be completed.
It would help in deciding what task could be taken for work at the moment and to estimate what effort need to be done to accomplish context or project (in addition to # of tasks displayed at the very top of the page).
Small 3-digit box near task description in "Add a next action" menu would be enough.
One more related feature is to allow fixation of elapsed time (in similar 3-digit box near task description in context or home page).
That would facilitate in creation of activity reports (how did I spend a day). They are not timesheets in any case but may help to understand in what task(s) I invested (wasted) so much time also serving as a source for time management improvement.
It would help in deciding what task could be taken for work at the moment and to estimate what effort need to be done to accomplish context or project (in addition to # of tasks displayed at the very top of the page).
Small 3-digit box near task description in "Add a next action" menu would be enough.
One more related feature is to allow fixation of elapsed time (in similar 3-digit box near task description in context or home page).
That would facilitate in creation of activity reports (how did I spend a day). They are not timesheets in any case but may help to understand in what task(s) I invested (wasted) so much time also serving as a source for time management improvement.
Leave a comment
I noticed that this is done in nozbe via a pulldown. Most of the time I ignore it but sometime's it's handy in getting a sense of how long the total project will take.
They chose to implement it by populating a pullown w/ about 10 interval, 5,15, 30, 45, 1, 1.5...8hrs. Seems like a pretty reasonable approach.
Possible use for reporting in the future? estimated at 2hrs actual 3.5hrs...
They chose to implement it by populating a pullown w/ about 10 interval, 5,15, 30, 45, 1, 1.5...8hrs. Seems like a pretty reasonable approach.
Possible use for reporting in the future? estimated at 2hrs actual 3.5hrs...
Migrated to GitHub issue #276