I agree with you. It should be improved. The whole Goals feature would need to be enhanced in several ways. BUT, in the meantime, let me tell you how I deal with this. I hope it can help you as an interim solution.
1) I name all my projects with a prefix, such that I can see from the prefix which Goal it belongs to. Further, I keep my projects list sorted (manually) such that all projects that belong to a certain goal are adjacent to each other in the projects list. This also means that when I look at, say, the next actions lists grouped by Project, all tasks that belong to a certain Goal are at least listed consecutively (but under separate Project headings, of course, and I cannot get all the high priority from the whole Goal all placed at the top of the Goal etc etc, but still ... better than nothing)
2) I generally put every task into a Project (and every Project belongs to a Goal). For "single" tasks that do not actually belong to a real project I have a number of permanent "phony projects" that serve as "area containers" - one for each area of responsibility. I have ten of those Projects and the contain all my miscellaneous tasks in each area. This makes it easy to review my lists in a systematic manner and to find what I am looking for.
Goals Not displaying
It's very useful, when reviewing tasks to see the context and project shown next to the task. The only list where you can see goals is next to projects. If you can allocate a single task to a goal, why can't you then see that listed along side the task
-
05/14/2015 11:35#1PRO
-
05/14/2015 21:02#2PRO
@Folke some good ideas there. May I borrow them? :)
-
05/16/2015 15:44#3PRO
Sure, go right ahead!
At least it is a way to get by until a more solid Goals feature is developed.