defect? Can someone reproduce

[Lisa Stroyan]

Can someone see if they have this same defect?

Create a task "test"
set under recurrance, regenerate daily or weekly
set a start day of a couple days ago, and a due date of 12 weeks out
click "lock period"

Now complete the task.  My next start date jumps back into July.  this doesn't happen if the task is due 1 week away, or if lock period is not set, or if it is set to recur daily/weekly instead of regenerate.

Lisa

---

Lisa Stroyan, li...@stroyan.net
www.empathic-parenting.com

[Ron]

Hi Lisa,

I confirm as I get the same result.

I set my recurrence to regenerate daily, with start date October 4,
2009, and with a due date of December 29, 2009. When I completed the
task as of October 6, 2009, the task recurred but with a July 13, 2009
start date, and a October 7, 2009 due date.

It is a weird result, but recurrence works off of due dates, not start
dates. So when you complete a recurring event on October 6, MLO
changes the due date to October 7 (one day after completion), keeps
the same lead time, so moves the start date back into July.

I think MLO is operating correctly. Setting up a recurring event to
start and end over a 12 week, 2 day time period, and then completing
that task 2 days after you have started it, is kind of weird in itself
though. What exactly are you trying to achieve and what result did you
expect? I expect there is a way to achieve what you are looking for by
choosing the appropriate set of recurrence parameters.

Ron

On Oct 6, 8:00 am, Lisa Stroyan <l...@stroyan.net> wrote:
> Can someone see if they have this same defect?
>
> Create a task "test"
> set under recurrance, regenerate daily or weekly
> set a start day of a couple days ago, and a due date of 12 weeks out
> click "lock period"
>
> Now complete the task.  My next start date jumps back into
> July.  this doesn't happen if the task is due 1 week away, or if lock
> period is not set, or if it is set to recur daily/weekly instead of regenerate.
>
> Lisa
>

> ----------
> Lisa Stroyan, <mailto:l...@stroyan.net>l...@stroyan.netwww.empathic-parenting.com 

[Lisa Stroyan]

At 11:40 AM 10/6/2009, you wrote:

It is a weird result, but recurrence works off of due dates, not start
dates. So when you complete a recurring event on October 6, MLO
changes the due date to October 7 (one day after completion), keeps
the same lead time, so moves the start date back into July.

I see what you mean. 

I think MLO is operating correctly. Setting up a recurring event to
start and end over a 12 week, 2 day time period, and then completing
that task 2 days after you have started it, is kind of weird in itself
though. What exactly are you trying to achieve and what result did you
expect? I expect there is a way to achieve what you are looking for by
choosing the appropriate set of recurrence parameters.

I was playing around with options for whoever asked about recurring/regenerated tasks with no due date.  I was trying to figure out ways he could set the due date off into the future so that it wouldn't be "due".

As I mentioned in another post, I work around this by recurring weekly/daily, but it would be very handy to have recurring tasks that don't have a due date.

[Andrey Tkachuk (MLO)]

I will look into it.

A.

On Oct 6, 4:00 pm, Lisa Stroyan <l...@stroyan.net> wrote:
> Can someone see if they have this same defect?
>
> Create a task "test"
> set under recurrance, regenerate daily or weekly
> set a start day of a couple days ago, and a due date of 12 weeks out
> click "lock period"
>
> Now complete the task.  My next start date jumps back into
> July.  this doesn't happen if the task is due 1 week away, or if lock
> period is not set, or if it is set to recur daily/weekly instead of regenerate.
>
> Lisa
>