Quote:
Originally Posted by Brian
For what it's worth, I use no due-date actions set to "Start again [X days] after completion" for this. Once I do it, the action hides itself for a few days, then reappears and stays visible until I do it.
|
I tend to do the same as Brian - i.e. start date task with "start again"
I wonder if the issue of the checklists relates to the concept of "should"? If a maintenance task is showing up more frequently than useful, it may be worthwhile to decrease its frequency.
Another thought might be to create the list as its own project. Set that project itself to have a start date and a start again frequency. Then use a separate project to carry tasks addressing the Should task list.
In other words, one project has your "shoulds". The other project has repeating tasks to perhaps remind you to print a report of the list with the Availability filter set to "Any Status" at some set frequency. This would effectively show what was able to be completed and what wasn't. After printing the report, you could then check off the remaining tasks in your Should list so that it resets with a new start date.
If no report is needed, then instead use the task in the maintenance project to alert you as to the Should's list expiration. For extra credit, you could add a link to the Should list from the maintenance task using the Copy as Link functionality.