Reoccurs/due date of task after completitnion of another task

[grizz]

Hi,

I want to have two task:

X - reoccurs month after completition

Y - reoccurs month after completition and it's start/due date should be 2 weeks after completion of X.

How can I achieve this?

[Dwight]

Hi, grizz. I have to ask for a little more information. Does Y always happen two weeks after X? 

Task Y apparently starts and is due all on the same day. Is the same true of X, or dues X actually involve some lead time?

A lot of times when people are using "reoccurs one month after completion" rather than "reoccurs every one month" it is because the task does not reliably get done when scheduled. Some times it might happen every month, other times there might be a few months elapsed before it gets done. Is that what's happening for you?

In this scenario, the "one month" is like a minimum wait time. After you do X, you may not do it again the next day or the next week, you have to wait a month.What happens if you do X on January 1 and Y has start and due date January 15 but you do not get around to doing Y until Feb 7. Does X happen again on Feb 1 or does it have to wait for Y to happen? If X happens on Feb 1 does Y get rescheduled for Feb 15 or does it remain overdue for Jan 15? After Y happens on Feb 7 is the next Y Feb 15 (two weeks after X) or Mar 7 (a month after Y) or both?

The scenario is a little confusing to me because there are two different formulas for scheduling Y and I don't know what to do if they give different results. If you can explain how this would be supposed to work, I will try to see hoe that could be coded.

-Dwight

[grizz]

Hi,

Both X and Y are one day actions.

I want to achive somthing like postponing starte date of task:

In ideal scenerio: X should be done on 1 day of month, Y on 14th. But if  Finished X not on 1st but ex. four days later, Y should be started/due on 18th and then next occurrence of X on 5th and so on.

[Elizabeth Lindsay]

Have you tried using the Delay feature? Not sure if it fits what you are looking for.

[David Timpe]

I think this works if I understand the request correctly.

Task "X" with start date of 1/1/2018 and due date of 1/1/2018.

Task "Y" is sub-task of "X" with start date of 1/15/2018 and due date of 1/15/2018.  

Set recurrence of Task "X" to "Reoccurs 1 month after this task is completed...".  

This establishes "Y" as occurring 2 weeks in the future relative to "X".

Now complete "Y" leaving only "X" incomplete.  

You now have only "X" as due on 1/1/2018.  

When you complete "X" today (1/13/2018) the branch reoccurs.  "X" will reoccur 1 month from the date of completion which is 2/13/2018 and "Y" will reoccur 2 weeks after than on 2/27/2018.  

[Dwight]

On Saturday, January 13, 2018 at 4:09:05 PM UTC-5, Elizabeth Lindsay wrote:

Have you tried using the Delay feature? Not sure if it fits what you are looking for.

Hi, Elizabeth (hi tigger)

It's very challenging to set up dependencies with repeating tasks, because the dependency is satisfied when the independent task is completed, however recurring tasks are never completed, they just reoccur.

To explore this, create a recurring task and a simple task with the simple task dependent on the recurring task. (for simplicity sake do not create a delay for the dependency). In the advanced recurrence options for the recurring task, select that you want a completed copy of the task created whenever the task reoccurs. The dependent task is inactive because the task on which it is dependent is uncompleted.

Now complete the recurring task. You now see two copies of that task, one with the original schedule and completed, and the other with a future schedule, recurring and uncompleted. If the dependent task were dependent on the completed copy then the dependency would be fulfilled. But it is not. It is dependent on the uncompleted, future, recurring copy. No matter how many times you complete the recurring task, the dependent task's dependency remains unsatisfied.

The only way that the dependency will ever be satisfies is if the recurrence options for the repeating task specify a maximum number of reocurrences, and that maximum is reached.

[Dwight]

Hi, David. If I understand your suggestion, on 14Jan18 X and Y will be
uncompleted tasks, with X as the parent and Y as the child, and with X
dated 13Feb18 and Y dated 27Feb18. Is that right?

If that is correct, then from 14Jan18 through 26Feb18 both tasks will be
inactive. X will be inactive because of an uncompleted subtask and Y
will be inactive because of a future start date. On 27Feb18 task Y will
become active, but X will remain inactive due to uncompleted subtask.

It would diverge from the given use case for the user to perform Y
before X but that would be what the tasks would call for. If/when the
user eventually completes the instance of Y scheduled for 27Feb18, then
X will become active, dated 13Feb2018 but already overdue.

-Dwight

> --
> You received this message because you are subscribed to the Google
> Groups "MyLifeOrganized" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mylifeorganiz...@googlegroups.com
> <mailto:mylifeorganiz...@googlegroups.com>.
> To post to this group, send email to mylifeo...@googlegroups.com
> <mailto:mylifeo...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/mylifeorganized.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mylifeorganized/35f6377a-ce89-4370-a381-19e9ddb9708d%40googlegroups.com
> <https://groups.google.com/d/msgid/mylifeorganized/35f6377a-ce89-4370-a381-19e9ddb9708d%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.