Due Numbers & Repeating Actions

[SpiralOcean]

I have actions that repeat daily in a
Process Collection Buckets context.

Currently, they always show due when I complete them, because they are within 2 days for the Due Numbers. (I like having 2 days for the due numbers, it's going to change my life.)

I had the idea of just completing action items so I was completing actions that are three days in advance to get those numbers off. (I love the numbers)

However, when I complete an action that is due tomorrow, it creates another action due tomorrow, not due two days from now.

This is expected behavior... and makes sense. But it conflicts with the due numbers philosophy.

Something needs to change... I'm not sure how yet.

One suggestion is to have a due date that is three days from the start date.

Then I could group by the start date for the item.
complete it
the start date changes to tomorrow, and the due date three days from tomorrow.

If I don't complete it, tomorrow it will show up in my due date numbers.

If you think this is a good idea, please submit it to OmniFocus using the send feedback button on the application. OmniFocus prioritizes requests based on the number of requests they receive.

Or maybe there is a better way. I'd love to hear it.

Thank you.

[eronel]

However, when I complete an action that is due tomorrow, it creates another action due tomorrow, not due two days from now.

Have you checked to make sure that in the Repeat Inspector the task is set to repeat from the assigned date rather than from the completion date?

[SpiralOcean]

Ahhh... thank you eronel.

They are all set to completion date.

And that does let me complete out to the future.

The problem with this is it will mess up reporting, or viewing completed items.

Lets say I don't do a task for a week. I finally get to it and complete it.
If I use completion date, it shows up in my tomorrow list.
If I use the assignment date, I have to complete it 7 times to get it to show up for tomorrow. And the reporting shows that I successfully completed the item 7 times, instead of reality of I only completed it once.

For items that slip... and I know that never happens... ;-)... but if it does happen, completion date is the correct choice.

Unless, OF develops a way to complete an item that was due in the past, and assign it the next due or start date in the future... besides using the completion date. :-)

[eronel]

This touches on something that has been niggling at me: there's no such task status as "skipped" or "dropped." Only projects as a whole can be marked as dropped. But there have been occasions where I wanted to maintain a record that I had planned a certain task but decided not to do it.

Hmmm.... I suppose I could create an inactive context called "dropped" or something to show this, but conceptually it seems strange.