You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find myself updating the notes on a project's next action a lot as things change, or when I shift the action from some context to @waiting For. It would be neat if a history was kept every time the notes field was updated. This would create a journal or diary on each task as it was updated.
On April 4, 2007 at 13:37:37 (+0200), Anonymous commented:
Interesting. Just to clarify, do you mean that you edit the actions's notes, or a project note (i.e. one attached to a project, rather than a next action. I know it means doing it manually, but you could just keep all the previous notes, and add the new one at the top or bottom, prefixed with a timestamp. I'm not sure how much extra a history (stored separately) would give you, particularly as the notes are hidden by default anyway, so you're not cluttering the view by adding more notes.
On June 6, 2007 at 09:19:18 (+0200), Anonymous commented:
yes, I edit the action's notes. What you've described for the project's notes is almost exactly what I imagined for the action's notes. As I complete tasks I'm often updating the notes with more information, and as I suggested this by deafualt creates a journal or diary if each version is stored. Not sure how you'd display it. Maybe just the latest with an option to view the history.
Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/503
I find myself updating the notes on a project's next action a lot as things change, or when I shift the action from some context to @waiting For. It would be neat if a history was kept every time the notes field was updated. This would create a journal or diary on each task as it was updated.
hifi@alphalink.com.au
Originally reported by Anonymous on April 4, 2007 at 16:31:00 (+0200)
The text was updated successfully, but these errors were encountered: