Repeating projects; not keeping the completed instances
 

I have some projects like "Clean bathroom" that I want repeated at some specified interval after completion date, but when I complete the project, I don't want the completed project (instance if you will) left in OmniFocus. It appears the simplest way to do this is to mark the project as complete, then delete that version (since a new one gets created once the other is marked complete). Just checking if I'm missing any better method.

In a future version it might be handy to have an option in the Repeat Inspector to delete the Project or Action when complete, perhaps even regardless if the repeat is based on Assigned or Completion Date. Thanks.

Bob

Hey Bob,

I'm the same way.

Here is my process.

Instead of using a due date, use a start date.

Then in your filters, set your action filter to available.

You will only see actions that have started.

There is a bug with OmniFocus right now with repeating actions based on completion date.

to work around, use the based on assignment date option.

here's more info on the bug.

Completing a repeating action that will generate new dates based on completion date, uses the due date as reference and not the start date.

Example: (brian is my support ninja on this one)
Thanks for the follow up Brian.

Still having problems with this... however, at least the start date isn't jumping backwards.

Here is the test case:

test action startdate= 11/26 enddate=11/28
repeat daily on completed

the task starts off with the following startdates & endates and todays date is 11/30
11/26 11/28
complete it once
11/29 12/01
complete it again...
11/29 12/01

And therin lies the problem.
If todays date is 11/30
I still see that task to do.
But I've already done it. And when I mark it as complete, it won't advance to the next start date.

I am filtering by available tasks
There is no way for me to make that task go away.

I've completed the task for the day, but it still says I need to do the task.

The start date is what should be used for the next date generation.

This same process works correctly on completing based on assigned date.

Let me know if there are further clarifications or questions.

-------------

Let me know if I wasn't clear on this one.

I use to use due dates for all my actions... now it's all start dates. I only use a due date when I want a red or orange number to show up.

Update from Omni. If you think this is a bug, please send to Omni.

Hello Brian,

How does this work with items that repeat daily?

When I use the available filter, and complete an action.
The action says it is still available.

This seems like a bug to me.

The problem with using assigned date...
If I missed 7 days, I need to complete it based on the completion date.

Otherwise, when I complete based on assigned, I must complete 7 days for the action to catch up.




On Dec 3, 2007, at 6:59 PM, OmniFocus Support wrote:


Sorry for the confusion here, but this isn't a bug. It's a two-day long task that's meant to repeat one day after completion. You complete it on the 30th, so the new due date is going to be December 1st. We step back two days and arrive on 11/29.

It really sounds like what you want is to switch to the "repeat from assigned date" setting. That way, we'll advance the start date in the manner you're describing. That uses the start date in the manner you'd prefer.

Sincerely,

Brian C.
Support & QA Manager
Omni Group

[QUOTE=SpiralOcean;27162]
test action startdate= 11/26 enddate=11/28
repeat daily on completed[/QUOTE]

The repeat period refers to the due date, so if you want your task to start the day after you complete it (and be due three days later) then you can get what you want by setting the repeat interval to three days rather than one day.

Does that help?

[QUOTE=Ken Case;27535]The repeat period refers to the due date, so if you want your task to start the day after you complete it (and be due three days later) then you can get what you want by setting the repeat interval to three days rather than one day.

Does that help?[/QUOTE]

It doesn't help. Here is why.

I want an action that is repeating daily.
To not show up in the available filter.
While using the completion date as my repeating action.

I have tried the following dates:
Start Completion
12/1 12/4
When completed
12/3 12/6
Still shows up in my available actions

12/1 12/5
When completed
12/2 12/6
Still shows up in my available actions

12/1 12/2
When completed
12/5 12/6
Still shows up in my available actions

When I complete something today.
The start date should advance to the future.
So I don't see the action until it is time to start.

Can you give me an example, why the current method of computing the next due date is used?

Why is the start date not used for repeating actions?

Our current assumption is that the due date is the most important date, so if you have both a start date and a due date the repeat interval is applied to the due date (and the start date is calculated as a lead time relative to that due date).

So, if I have a task with these settings:

start: 11/26, due: 11/28, repeat: every 3 days from completion

and I complete the task on 12/5 (today), I'll get:

start: 12/6 (not yet available), due: 12/8

The new due date (12/8) is the completion date plus three days, the new start date (12/6) is the new due date minus two days (because the old start date was set to two days before the old due date).

Isn't that what you're trying to do?

If you look in the repeat inspector, it will show you the Next Start and Next Due dates (assuming you completed the task immediately); you can check those to make sure you're getting the settings you want (without having to actually check off your task to test it).

P.S. — If you don't specify a due date, then the repeat interval refers to the start date: so if you've set a task to repeat one day after completion and it only has a start date, the new start date will be tomorrow.

Thank you for the response Ken.

How does the assumption that the due date is the most important,
fit in with the paradigm of how the available filter works?
If a task has a start date of today
a due date of tomorrow
it shows up in the available filter

when I complete it...
it shows up in the available filter.
when I complete it again
it shows up in the available filter.

From my perspective...
the action should no longer be available
because I completed it.

What about changing the logic so that...
if the item has a start date and a due date
and the current date is included or is in-between or after the due date
the repeat interval is applied to the start date
and the due date is calculated based on the start date

Can you think of any examples where this would cause a problem?

Here is another thread with the same issue I'm having:
[url]http://forums.omnigroup.com/showthread.php?p=27726#post27726[/url]

One interesting thought about this:
I used to ignore the start date, and just use due dates for everything.
Until those wonderful red numbers started appearing.

Now, I use the start date for everything, use the available filter, and use the due date for my hardlandscape.

That changed everything for me.

If an action has a start date & a due date and it is completed, it should move ahead to the next start date.

I can think of no examples where this would cause a problem.

I have a plethora of hard examples where completing using the due date causes problems. Let me know if you would like them listed.

Once an action or project is completed, and it has a start date and an end date, it should move forward into the future.

[QUOTE=SpiralOcean;27699]If a task has a start date of today
a due date of tomorrow
it shows up in the available filter

when I complete it...
it shows up in the available filter.
[/QUOTE]

Only in the case where the task repeat period is equal to or smaller than the duration of the task. Use ken's workaround - make the repeat duration greater than the length of the task - and this will not happen.

[QUOTE=SpiralOcean;27699]
What about changing the logic so that...
if the item has a start date and a due date
and the current date is included or is in-between or after the due date
the repeat interval is applied to the start date
and the due date is calculated based on the start date

Can you think of any examples where this would cause a problem?[/QUOTE]

The system you're suggesting here is more complex, which means it's more difficult for users to understand and to use.

It also requires more effort to code, test, and maintain going forward.

From a user perspeactive, if I have completed an action that has already started, and is not yet due, I would expect it to not be available to me.

The current method is confusing.