Forums / Help

Scott, are these 'every' or 'after' repeating tasks?

Notes (and all other properties) are shared between 'every' repeating tasks. So, if you change the priority of an 'every' repeating task, all other instances of that task will change too. Notes are shared between all instances.

However, notes and other properties for 'after' tasks are not shared. This is because 'after' tasks are considered to be new tasks -- they copy across the properties from the previous repeating task, but if you change a property (e.g. priority) then it will change for that task only.

There's some more discussion of notes for repeating tasks in this topic.

Posted at 3:09am on March 23, 2006

Emily, thanks for the information on "every" versus "after" and the reference to Argotnauts similar concerns.

I'm a power user of Outlook and have been for many years. What Outlook actually does for a recurrance is copy all the current attributes -- including the notes -- from the completed task to the new task. It does not share the information between these tasks, rather it stores each instance seperately. The net effect of this is a paper trail showing the changes from one instance to the next.

This feature exists so that decision makers (lawyers, project managers, sales people, etc) can identify what actions were taken when. In other words, it's an audit trail or a crude form of personal workflow. For many years, my business depended on it -- old habits die hard.

So, we know that the current priority, time estimate and tags are already copied from the old task to the new one in an 'after' recurrence. Why not the notes? Aren't they just another property? Shouldn't the user be the one to decide if that information is relevant to the next instance?

Posted at 4:01am on March 23, 2006

Replied on the other topic :)

Posted at 10:51am on March 25, 2006