As long as there is an active task in a tree, the parent will not show up in
any of your active lists. If you have multiple levels, they will bubble up to
the top as all children are taken care of. As soon as the last child is
completed, deleted, or hidden, the next level parent will show up as active
(green). What I sometimes do is label the parent task as the "finishing up the
project" task, then it acts like a final task.
I'm not at my desktop, but I believe that you can have as many child tasks as
you want with the first method that I described, though not the one that uses
dependencies. "Recur" just means that the task is moved to its next active
date. There is an option for weather completed task is created.
Even though the parent is recurring, it's basically just being moved out into
the future, especially if you click "do not create a completed copy". Because
the children do not have fixed dates, they inherit that the parent's. So in
effect, you're moving the whole tree to the next date that the next task is
going to be due, but you only see the first active task in your list based on
setting "complete subtasks in order" .
I'm not sure how you would mix tasks that are dependent on receiving client
input, and those that or not. You may have to have two subtrees under another
parent that groups all of the activities for that client. E.g, ( hopefully this
tree will come through using my phone)
Archive photos for client
Task that can be done anytime
Another task that can be done anytime
Make sure client is satisfied ( recurring task with advanced settings)
Send client proofs
Waiting on proof choices from client
Send client online album
Waiting on album approval
…
Other tasks for the project; may need to add dependencies manually
You don't want to make the parent a folder. If you do, it doesn't recur and
get completed in the way it has to for this to work.
Probably the easiest way to learn is to play with it. Create a test tree with
just a couple of tasks and the settings I described. Set the date of the parent
back into the past so you can see what happens when you completed the first
child. You can use undo to tweak settings and try again.
FischerPhoto <[email protected]> wrote:
>HI Lisa
>Thanks so much for responding to this and successfully distracting
>yourself from more important work :)
>I'm fairly new with this level of using MLO so am still a bit unsure.
>
>My main objective is to see one task per client appear at a time in my
>to do list and have a certain amount of time to get it done.
>And for some tasks ( like receiving client input) the clock for the
>next task only starts when the current task is complete.
>Seeing the task of receiving the input as incomplete in my to do list
>is good.
>Right now there are no subfolders just a parent with a list of tasks
>that have to be done in order, with the time to complete some tasks
>only starting when the previous one is complete.
>Does this set up match what you have outlined? I can't quite tell./
>
>It looks like the first option makes the most sense but I don't
>understand how the recurance works. Will the parent "photos for
>client" appear multiple times? Or will just the subtask appear? And
>how often?
>
>Here are more details of what I am trying to accomplish if you want to
>distract yourself some more :) I'm a wedding photographer, by the
>way. And picking out photos are for the album that will have multiple
>revisions with the client, so multiple ties that I am waiting on the
>client before the clock starts again to complete the new revision.
>
>I'm creating my client workflow.
>And this is the design so far:
>The client's name is the parent
>and under that are all the steps in one folder.
>Starting date is the shoot date
>The tasks have a certain amount of time to be completed.
>it works well to set the parent that all subtasks are done in order
>I want to see only one task per client to be done at a time
>It is fine to have in my to do's that there is a task to receive the
>client's photo choices
>The next step is to design and deliver the wedding album proof and
>there is a week to do that from the time that previous task is
>completed
>Then I have to wait for them to go over the design and give me changes
>that they would like
>I have a week from the time that the "task" of receiving the changes
>to revise the album
>
>Thanks so much Lisa!
>
>Jon
>
>
>
>
>On Mar 11, 1:35 pm, Lisa Stroyan <[email protected]> wrote:
>> See if this does what you want. Put the recurrence on the parent, ie,
>>
>> Photos for <client>
>> received client album choices
>> generate photos
>>
>> Set recurrence for "Photos for <client>" as follows:
>> - Starts at photo shoot date, due one week later, recurs one week
>after
>> this task is completed. *Advanced*: Automatically recur when ANY
>subtask is
>> completed, DISABLE automatic reset.
>>
>> - If you want " received client album choices" to be an active task
>until
>> the client gets back to you, you can use "complete subtasks in order"
>on
>> the parent. (or combine with option below)
>>
>> - If you don't, try this. Uncheck "complete subtasks in order". Put
>a
>> dependency from "generate" to "received". Then on "received", click
>"Hide
>> in Todo". It won't show up in your normal task lists until you get
>the
>> clients feedback.
>>
>> - Alternatively, you can set the start/due date for the parent to be
>when
>> you want to remind the client, ex. 3 weeks out (combine with option 1
>> above). So you would have:
>> Photos for <client>
>> received client choices
>> remind client to make album choices
>> generate photos
>>
>> Since you are using "recur 1 week later..." the brilliant thing is
>that you
>> can set the date for reminding the client out a few weeks, and still,
>once
>> you complete "received client choices", "generate" will be one week
>out.
>>
>> The only catch is that lead time is inherited from the parent. I
>think you
>> can play with the dates of the subtasks though and it will track.
>>
>> A fun challenge :) Much more interesting than the work I'm supposed
>to be
>> doing.
>>
>> Lisa
>>
>> On Sun, Mar 11, 2012 at 8:32 AM, FischerPhoto
><[email protected]>wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> > This may be a simple question but can't figure it out. Thanks.
>Tasks
>> > are set to be completed in order.
>> > I'm a photographer. Previous task is "received client album
>choices"
>> > I want there to be a week lead to complete this which will only
>begin
>> > once that task is "completed". I have set a week lead time. When I
>> > enter this info in, a date is generated as a week from the shooting
>> > date. And I want there to be no date generated yet. I want the date
>> > only to be generated once I complete the previous task.
>>
>> > Thanks very much!
>>
>> > -Jon
>>
>> > --
>> > You received this message because you are subscribed to the Google
>Groups
>> > "MyLifeOrganized" group.
>> > To post to this group, send email to
>[email protected].
>> > To unsubscribe from this group, send email to
>> > [email protected].
>> > For more options, visit this group at
>> >http://groups.google.com/group/mylifeorganized?hl=en.
>>
>> --
>> Lisa
>>
>> ------------------------------
>> Lisa Stroyan, mailto: [email protected] <[email protected]>
>
>--
>You received this message because you are subscribed to the Google
>Groups "MyLifeOrganized" group.
>To post to this group, send email to [email protected].
>To unsubscribe from this group, send email to
>[email protected].
>For more options, visit this group at
>http://groups.google.com/group/mylifeorganized?hl=en.
Lisa
--
Sent from my phone.
Reply directly to me at mailto:[email protected]
--
You received this message because you are subscribed to the Google Groups
"MyLifeOrganized" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mylifeorganized?hl=en.
