Quote:
Originally Posted by whpalmer4
If by "due items only" you mean only actions which have their own, explicitly assigned due date (not inherited from the containing project) you are out of luck unless you write an Applescript to traverse the database and generate a report of some sort. If that's the case, I'm not sure why you would want to ignore undated actions that are part of a project that is due -- surely that means the actions are due as well, no?
|
I want to prioritise and see the priorities as a raw bunch within contexts.
eg. I sit at my station and view all the next phonecalls - in any project, then make them, one by one.
That would mean that under the present protocols I would also need to see the undated items from due projects as well - which is too much information for the task at hand.
If I simply remove the due dates from the projects and assign them to the next action then I would lose the project due dates.
If I simply view the next action in a due project I am not seeing my prioritised actions.
eg. I have to create a project to conform 2 houses to legal requirements by jan 31st 2009.
This phone session, I only want to see the phonecalls I need to make today.
How do I set that up so that I can see those phonecalls, and only other phonecalls belonging to other today-type calls so I can exercise a single sitting of phonecalls without all the other data irrelevant to those phonecalls?
Quote:
Originally Posted by whpalmer4
Now, if by "due items only" you mean only actions which have their own, explicitly assigned due date OR are inheriting a due date from their containing project, then make a context view, group by due, close the grouping triangles for any groups you don't want to see (no due date, maybe due dates in the future as well if you only want to see overdue items), and save it as a perspective.
|
yes, I understand. And I will then see items with no due date because they are part of projects with due dates.
I guess I'll have to get used to it :-)
peter