Quote:
Originally Posted by brianogilvie
Otherwise you might find yourself making a few calls that are low down on your list in a parallel project (because the other actions are not in that context), and not getting to the 2 or 3 calls that are at the top of other parallel projects, and therefore the most important things to do to move those projects along.
|
That's a really neat strategy!
But I have trouble making it work. Maybe I've missed something -- is there a way I can see available tasks in context view not clustered by project?
If I switch from "next" to "available", I end up with a very long list, across dozens of projects. I don't have any grouping turned on, but I still find the available tasks listed in (project, priority) order. That means I have to look through the entire list to find the calls that are "at the top of other parallel projects".
Is there some way to bring the top tasks of projects to the top of the list?