Make an option to add recurence to Start date, not to Due date
According to GTD concept you should only specify the due date if this is really last day when the task can be done or it will be never done.
But the only chance to create a Recurrence task in MLO is to use Due date, because recurrence use Due date and can not use Start date.
I think that issue seriously limiting users to have recurrence tasks.
I think you should avoid setting Due dates for tasks wherever you can. MLO has good and adjustable priority and filtering settings to review all tasks without Due dates.
Andrey Petrov commented
Fletcher Kauffman commented
This is something I've always felt was broken with MLO, which is that the "start date" is not a start date in the sense that any other project management or task management software uses. Instead, it is the date on which the item will begin to show as active.
I agree--it would be nice to create recurring tasks with Start Date only. Like others, I prefer to reserve Due Dates for actual *hard* dates.
Also, somewhat related thread regarding making it easier to change the Date of a recurring task:
Ely Hofner commented
I strongly agree with Michael. The more I use the product (and I use it now for several years) the more "clutter" is there in the prioritized "due dates" with "fake" unnecesary "dues", negating the (in my opinion) the No. 1 advantage of MLO over other products - Priority Scores.
Furthermore, (again in my opinion) programming this should be very easy: just duplicating the same routine as the "due date" but with "start date" used for scheduling and the option not to have an end date. The user selects what routine to use in a specific task.
If I could only give more than 3 votes... What happens now is that recurring tasks get artificially high priority scores because of the requirement to have a due date -- higher than if they would be once-off tasks without a due date. This goes against the grain of almost any reasonable prioritisation concept, not only GTD.
This option would allow to leave tasks as 'available'. It would leave the 'Importance' criteria act without the incidence of a due date to order available tasks. It would avoid to clog the 'To-Do' View. Thank you for your consideration relatively to GTD Method.
Jenn Maus commented
I agree with this - I use recurring tasks but don't like having the fake due date. In related features, ToodleDo has an optional due date feature whereby the recurring task simply disappears when the time has passed, if it hasn't been done.
Currently, when recurrence is set MLO forces the creation of -both- a start date and a due date. I *think* that the requirement proposed by ArtemS would entail not only recurrence based on start date, but also the possibility of having a recurring task with no due date.