Hi Gary, Unfortunately, the repeating ticklers don't automatically bump their dates up to the next due date. You have to do that yourself. The repeating tickler will have a 'bump the date up' button (for lack of a better name for it), which makes bumping the due date up to the next due date an easy thing. The bump up button is a daily bumper for daily repeating ticklers, a weekly bumper for weekly ticklers, monthly for monthly, etc.
There actually isn't a 3-month 'bump the date up' button. What I did to handle this schedule was set my van service tickler up as a monthly tickler. Every time it comes due, I click the 'bump the date up a month' button three times. The van service schedule is easy to remember, so I don't need to keep a note about it. On other repeating ticklers, I'll sometimes put notes about their repeating schedule in the tickler comment area. It would be nice if the ticklers handled repeating due dates automatically, and it's possible that Simon might extend them to do so at some point (I have a vague memory of him saying something about that once). The manual 'click the bumper button' process we have now is surprisingly usable, though. I'm actually kind of fond of it. Stefi On Wed, Dec 31, 2008 at 2:15 AM, Gaz <[email protected]> wrote: > > Hi Stefi > > Many thanks for the detailed response. > > I have one more thing to clear up and that is, you say that if it is a > repeating tickler, you set an action and then bump the date up > (assuming that it requires more than 2 mins to do). From what you are > saying, it seems that you are manually setting the date for say, 3 > months time. The MonkeyGTD software gives you the option of once off, > weekly, monthly, annually. If I was to set weekly, can I assume that > even if I mark the tickler as done for this week, it will > automatically show for next week at the same time etc? rather than > having to manually bump the date by another week?? > > cheers > Gary > > On Dec 30, 6:57 pm, "Stephanie Smith" <[email protected]> wrote: > > Hi Gary, > > > > The way I use them is I set up the tickler and the tickler date and then > > forget about it, as one does. > > > > Some ticklers are for tasks, some are reminders. Reminders don't always > > translate directly into a task, so my ticklers don't always turn directly > > into next actions. > > > > For the ticklers that are tasks, when the tickler comes due, I do the > usual > > GTD thing and decide whether it's going to take less than two minutes to > do > > the task or more. If it takes less than two minutes, I simply do the > task. > > The tickler doesn't become a next action in this case because it gets > done > > immediately. If it takes more than two minutes, then I do one of two > > things: > > > > a) If the tickler is a once-only tickler, I convert it to an action (with > > the little 'make action' button) and I continue on with it the way I do > with > > any next action. > > > > b) If the tickler is a repeating tickler, I don't turn the tickler into > an > > action, because I need the tickler to continue repeating. In this case, > I > > bump the tickler's date up to whatever the next appropriate date is, and > I > > create a new next action for the task that the tickler has reminded me > > about. Then I proceed with the action the way I do with any action, and > the > > tickler continues as well. > > > > A few of real-world examples: > > > > I have a tickler to get my van serviced. It's a repeating tickler that I > > set to come up every three months. It takes more than two minutes to do, > so > > I need a next action for it when it comes up. It's a repeating tickler, > > though. If I changed the tickler itself into an action, I'd lose the > > repeating tickler, and I don't want that. So, when the tickler comes > due, I > > create a new next action, name it "Get the van serviced", set its > context, > > and handle it in the usual way. As soon as I have the next action > created, > > I go back to the repeating tickler and update its tickler date to be > three > > months in the future. > > > > I also have a tickler to pick up my cleaning in about three days. It's a > > one-time tickler -- that particular batch of cleaning will only ever be > > picked up once. The tickler's task will take more than two minutes, > > however, so I will need to create a next action for it once the tickler > > comes due. So, when the tickler comes due, I'll click the tickler's > 'make > > action' button and turn the tickler into a next action. I'll give the > next > > action a context, and then I'll handle it the usual way. > > > > Finally, I have a tickler for a one-time transfer I need to make between > two > > online bank accounts. It's a one-time transfer, and the task will take > 30 > > seconds, tops. So, when the tickler comes due, I'll pop up the bank > account > > site, make the transfer, and then mark the tickler done. No next action > > needed because the task will be a 'less than two minute' task. > > > > Does that help at all? > > > > Stefi > > > > On Tue, Dec 30, 2008 at 12:46 AM, Gaz <[email protected]> wrote: > > > > > Hi > > > > > Apologies, should have said that I am using Monkey GTD 3.0 alpha > > > r103230. > > > The reason I say "supposed to" is that I am trying to understand how > > > to have a tickler (reminder) but also have an action as a result of > > > that. > > > > > cheers > > > Gary > > > > > On Dec 29, 5:25 pm, Ken Girard <[email protected]> wrote: > > > > Which version of the various TiddlyWiki GTD systems are you using? > > > > The most common ones are D3 & MonkeyGTD, but there are a couple of > > > > others out there as well. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GTD TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/GTD-TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
