repeating/recurring tasks bug

[sttrebo]

quick one, hopefully an easy one to fix. I was having a problem with a task recurrence which was driving me crazy. I had mistakenly added rec:+1b instead of rec:+1d. can you add (or check if working) a filter for allowable characters (dwmy only) in the rec: string?

[topas-rec]

b is an allowed character. It only counts business days.

That does not solve this issue of course. Just for information.

[sttrebo]

hmmm, i had some strange behavior when i used it.

(A) Review NCMR Log +Admin @Work t:2017-12-22 rec:+1d due:2017-12-22 - works fine, both due and threshold increment properly

if I change the d to a b then mark the task as done, I get this: (A) Review NCMR Log +Admin @Work t:2017-12-22 rec:+1b due:2017-12-25

then if I mark it as done again I get this: (A) Review NCMR Log +Admin @Work t:2017-12-25 rec:+1b due:2017-12-25

it seems that with the 'b', the due and threshold dates don't increment properly.

[topas-rec]

The first repetition seems correct (jumping over the weekend...) The second one should be due on 26th I think.

[sttrebo]

incrementing to the 25th is correct, but you notice how the threshold date doesn't increment the first time i mark it as done, takes a second time to increment it properly. if i use +1d then both increment properly.

[topas-rec]

I see. That is wrong.

[sttrebo]

i know i should learn python to help out a bit (on my list), but any chance on a fix for this?

[topas-rec]

On my list. Looking forward to find some time. Thanks for the reminder.

[topas-rec]

What is the logic of the threshold date and recurring tasks? Should the new threshold date have the same (positive or negative) time delta as the old threshold date in comparison to the old due date?

[sttrebo]

for my workflow, the threshold date should follow the same time delta as the due date. Me personally, I don't see a workflow otherwise.