Kristoffer Balintona <krisbalint...@gmail.com> writes: > So, to be clear, you find that having an org project/todo heading for > each email thread suffices, since (i) all todos in the same thread end > up under the same project which makes (ii) finding outdated todos easier > since you see all todos for a thread together.
> If that’s right, then am I right in saying that it doesn’t directly > address the problem of todos associated with emails becoming stale > (e.g., additional emails being sent in the thread that invalidate a > task, causing it to become unnecessary or modification in its details)? > Grouping email tasks by thread might make it easier to stumble upon such > stale todos, but if simply forget that a thread has associated todo(s), > then those stale todos would remain. I see your problem and I think that you are approaching it from a wrong direction. Rather than looking at an email thread and trying to find "lost" todo items, I simply rely on Org mode keeping track of todos for me. If a todo must be done within certain time, I assign deadlines. When I start working on something, I schedule. When I need a group of todos to be all done, I use project and "stuck projects" agenda view. So, by using agenda and apropriate scheduling/refiling, I can make sure that nothing that should be done is lost, while "wishlist" things are not overwhelming me. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
