Here is a thought I wish to share with you.
We all have meetings, we all do errands etc, and quite often aim to do a well selected subset of our possible actions as one “batch” (to be done in one single errand run or in one single meeting)
say you have 30 @Errands on your next list, and you decide that 5 particular ones of those would be very good to do in one single trip sometime in the near future because they are all to be done in the same far-away place - and by limiting it to just these five it still won’t be to much to do in one run.
say you have a big bunch of things all in all to discuss with @Accountant or @John or @Staff, but want to narrow it down to a nice set of issues to bring up for discussion during the very next meeting, which perhaps has not been firmly booked yet but is expected to take place soon, and you prefer to have the issues identified now already.
It would be extremely nice, and useful, to be able to manage these actions in several ways at the same time:
- keep them in the original project where we need to have them in order to be able to review the project
- also keep them in a “batch project” where we can have them handy and review what items we have chosen so far
- be able to see the whole Batch item on a single line on the Next/Focus lists, rather than drowning in a bunch of individual actions for each errand or agenda point
- be able to see the whole Batch item as a separate Project in the left menu (if we want to)
What would be some possible ways to deal with this? What would be the ideal way? Here are some different approaches.
The ideal way probably would be if I could create a new project for this, which I could plan or schedule or whatever, just like any other project - which would be logical particularly if this “batch” would have been defined as a project if it were not for the fact that the actions already belong to some other projects. So, an action would need to be able to have more than one parent. But this is probably a bit complicated, especially with deep hierarchies and advanced project logic.
Obviously, one workaround is to invent a new “event tag” for each such batch or agenda instance, and make it a habit to filter for such special temporary tags etc. But being able to see these “projects” directly in the project list, and have them come up as a “project with sub-actions” etc on the next/focus lists would be awesome. Besides, it is messy to fiddle with tags in that way (I have tried). It is doable, but not very convenient and has limited uses…
Perhaps the most realistic solution would be if we could create Actions whose subtasks are in fact “linked copies” of selected other tasks. Like this:
All the various errands or whatever stay exactly where they are, in their respective projects. We create a separate Action for the batch task, e.g. “Meeting with John” or “Drive to Suburb65”. When creating subtasks to this batch task we somehow manage to select and link the various real tasks (but without moving them). They get represented (in the batch task) as subtasks with their original name and project, and are clickable (should we want to see additional info in the original task). The original tasks should all remain in place etc, but it would be good to have some (clickable) icon etc indicating that this task has been selected for a certain batch/agenda. When we check off the batch task all the individual subtasks automatically get checked off within their respective projects.
I think this last (third) approach would be fully viable, but don’t worry. No one has such features. It is just something I always dreamed of. If you will be the first to have it, you might benefit greatly from it, because I am sure many people would just love it when they see it in action in a smooth easy-to-use way. But if you don’t implement it nobody would know that the possibility even existed, so you’re quite safe.