Hi All, I'm using Contexts for people I assign tasks for. I've deleted
all the Contexts I don't use (I don't use them...) and created Contexts
with people's names.
On Tuesday, 17 April 2018 at 23:37:22 UTC+10 MG wrote:
> Hi Aiman,
>
> For your need I used to add a dependency task, I mean
Hi Aiman,
For your need I used to add a dependency task, I mean the task that need to be
completed will dependent of specific task.
For that, got to Dependencies section in the task properties panel and add the
apropriate tasks.
On the Delay field set the time for it to wait and, as soon as
Hello Aiman,
When I delegate a task or I'm waiting for input from someone, I set the
context to "?Waiting" and I put the person's name at the top of my task
notes, with a ? tag for example: ?Joe Smith. That way, when I'm talking to
Joe Smith about something, I can quickly search my outline for
Hi,
For me to deal with those aborted task meanwhile not to delete it, I will
use "Hide the branch in To-do" or Alt+E and leave a remark in the note
section remind me why I do not complete the task.
These tasks will be grey out and remain in the task structure.
^^
Regards,
LEW
On Friday, 13
This is a very good discussion!
Any advice on how do you deal with "Waiting for customer input"?
I deal with a lot of tasks/projects, and a lot of the times, I have to wait
for a response which can take days or weeks (and I don't have control).
I struggle when I try to manage these in MLO.
On
For that purpose, I use to add a subtask to the task, so that it becames
unactive.
I give that subtask a "waiting for" context.
Olivier
--
You received this message because you are subscribed to the Google Groups
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving
I agree that it is important to be able to record a task as not done /
aborted / superseded. Not many task managers have an easy way of doing
that. The way I do it in MLO is to have a category "-Superseded", which I
set when I check the task off. I have an autoformatting rule to set a
little,
