NOTES DISAPPEARING ON RECURRING TASKS
(closed account) says:
Notes attached to recurring tasks are not being reassigned to the new task generated upon completion.
The problem appears to have begun on Tuesday.
Prior to Tuesday, I have numerous examples of completed tasks where the notes rolled forward properly. After Tuesday, I have none.
Please look into this soon. I use the notes feature extensively to associate names, phone numbers and addresses with on-going tasks.
It's really awesome -- when it's working properly!
The problem appears to have begun on Tuesday.
Prior to Tuesday, I have numerous examples of completed tasks where the notes rolled forward properly. After Tuesday, I have none.
Please look into this soon. I use the notes feature extensively to associate names, phone numbers and addresses with on-going tasks.
It's really awesome -- when it's working properly!
emily (Remember The Milk) says:
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.
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.
(closed account) says:
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?
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?
emily (Remember The Milk) says:
Replied on the other topic :)