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.
Ely Hofner
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.
Ely Hofner