ForumsSearch
Search results for "Posted by "
| Author | Message |
|---|---|
|
jeff.covey |
This has been discussed by many people and promised for many years. I do hope it will finally happen.
|
|
jeff.covey |
Posted Nov 10, 2008 in: What's the difference between > and = in due dates?
Score: 0
Posted by Toodledo:
No, you are not missing anything. The booklet currently does not obey the = and > flags. We hope to get this fixed soon. is there any news on this? my booklet is still printed each time with items scheduled for six months from now, and i have to go through and scratch such things off before i can see what's actually useful on the lists. thanks, jeff |
|
jeff.covey |
Posted Aug 11, 2008 in: What's the difference between > and = in due dates?
Score: 0
just to add my voice to the choir, i'd really like the booklet to honor "=" and ">", and also not to print items with start or due dates that are, say, 14 or more days in the future. my booklet always prints my annual january 1st recurring items, which aren't useful to me here in august.
|
|
jeff.covey |
Posted Aug 11, 2008 in: managing projects with sequential tasks
Score: 0
how do people use toodledo to handle projects that have a number of
sequential tasks? for example: you need to wait for a reply to an email from someone, and then, based on that, call another person, then, based on that conversation, decide whether to do this or that. if you make tasks like this subtasks in a multi-step project, you can't put the subtasks in their proper order, and the main task is either done or not done; you can't have *this* waiting on *this*, waiting on *this*. in the example above, the first item would need to be put into status "waiting", and everything else would be waiting on that, so none of the tasks would be visible. i would just see the first one when i go into things with status "waiting". when it was marked as completed, the next item would need to become visible. my workaround for doing this has been to put the first step in a project as a task and put the subsequent steps in the note for that task. as i do one step, i change the name of the task by cutting and pasting the next line from the note. this is tedious, and doesn't let me set a different context, priority, note, etc. for each step of the way. does anyone have a better way of doing this? thanks, jeff |
|
jeff.covey |
Posted May 12, 2008 in: Addition of Start Date and Status
Score: 0
thanks for this! i'm looking forward to trying it out. it will be much cleaner than the workarounds of marking "someday" items with -1 priority, tagging tasks with "@waiting", etc. i second the suggestion of having start dates carry forward on repeating items. my todo list is always cluttered with upcoming items i don't need to see now.
|