SES21
My feedback
10 results found
-
26 votes
An error occurred while saving the comment SES21
supported this idea
·
-
15 votes
An error occurred while saving the comment SES21
commented
I agree that the Start Date change should be allowed, perhaps with a warning, but I wouldn't want UTL to automatically change my assigned due date. People use the date fields to suit their own particular system so, while you might want the due date to change too, I might not. Maybe I'd like to know that original due date & the fact that it wasn't started until after it was due...
-
9 votes
An error occurred while saving the comment SES21
commented
Please, please, please implement this! Almost all of my alarms are 12 hours off &, if I check something off in UTL that repeats, the due time is set 12 hours off for all following occurrences, too. Yes, I could put 12:00 due time on all those tasks in TD but that's a lot of effort & wasted bandwidth on syncs!!
SES21
supported this idea
·
-
124 votes
An error occurred while saving the comment SES21
commented
Newer phones don't have a search button & it takes a long press on the home button to bring up search already.
-
59 votes
An error occurred while saving the comment SES21
commented
When I do that, I usually just put the actual completion date in the note field.
-
98 votesSES21
supported this idea
·
An error occurred while saving the comment SES21
commented
I agree more snooze times are needed but, rather than go full custom, I'd prefer to see something in line with what TD has for alarm periods (although TD could stand to add a few more choices, too). Please at least add the 8/12/16 hours already requested & I'd also like to see multiple days like 1 through 7, 14 & 30.
-
56 votesSES21
supported this idea
·
An error occurred while saving the comment SES21
commented
Being able to set global defaults like this would be a big time-saver! Then we could just change those settings within specific views if desired...instead of having to set the same thing almost everywhere!!
-
86 votes
-
121 votes
An error occurred while saving the comment SES21
commented
Contexts should indicate a person, place or tool that's *required* to complete the task. If you can do it at home or work then neither of those is really a "context" for that particular task. I suspect, though, that there is something that's required to be able to do it - e.g., a PC, internet connection, telephone, etc. I agree with dd: if you need multiples, use tags instead - that's their purpose!
-
9 votes
Yeah, what he said! I use Due After a good bit, sometimes those tasks have real Start Dates too so faking it isn't an option, & I find it hard to believe that UTL doesn't truly support this.
Besides the above, you're overlooking the fact that we can't set a reminder on a Start Date, which means that we still need a Due Date (at least in TD) which would have to have an erroneous modifier since it can't be Due After! Also, if we don't put a Due Date, then that changes the Importance calculation & throws that all off, too. TD also treats the Start Date & modified Due Date differently when it comes to hiding Future Tasks. "Future Tasks" are hidden until their Start Date while tasks with modified Due Dates are only hidden until a week before they are due unless their start date keeps them hidden longer. That means, if we use your method, we wouldn't have visibility of that task until the day it was "due after" - which puts a kink in my workflow or takes me back to needing to use the Start Date field to make it show up the week before like it should have! But wait, I can't do that because it's already occupied with my Due After date! *Face Palm*
Based on what I read in TD's API doc, it's a matter of a single-digit value & you're already dealing with that field for BY, ON & OPTIONAL. How can this be so hard to implement?? If it's a matter of the characters following the Due Date in the UTL GUI, just use (After) instead of the whole phrase...