[whpalmer4]

Originally Posted by Greg Jones

Yes, if the original due date was set for the first day of the month. One month means from a particular date of the month to the same date the following month. The 15th of July will repeat again the 15th of August. The only deviation from this is if the next month does not have that particular date. If that's the case, then the next repeat will happen on the last day of the month. As example, a task created as due on January 31 will be due again February 28, again March 31, and again April 30...

Actually, it doesn't do that. If you set it for 1 month, due on the 31st, as soon as you encounter a month with only 30 days (or 28 or 29), it will be due on the 30th (or the 28th or 29th), as will be all subsequent repeats. It won't reset back to the 31st. You can verify this by creating a test action set to repeat every month, due on the 31st. Bring it up in the inspector and put in the 31st for the completion date. Inspect the newly created item, put in a completion date for it, continue the process until you have seen enough...safest thing to do is probably to set end of month items to be due on the 28th, and send in another vote for richer repeat controls via Help->Send Feedback.

As it stands, the only way the code could know to do the reset is if it kept track of the original date used in the chain, otherwise there's no way to know whether a repeating action with a date of the 30th was supposed to repeat on the 30th, or the last day of the month. If you're going to put in the code that handles that case, you might as well put in the rest of it, too.

[Greg Jones]

Interesting. I thought I had set up a repeating task in the past that handled this as described, but I just tested it and indeed it works as Bill described.