Jerud Yes, this absolutely. Except in Legend the new one should go above. I also think the new one should be a duplicate of the original repeater, so it doesn’t reflect any unique edits or notes I’ve added to the just-completed instance. This is easy to say, but tricky when you get into the details. Such as: what if you want to actually edit the original so all future instances change? They need to all be kept together in some way that allows reasonable access and editing without being in the way or creating sloppy messes with the surrounding Outline.
I’m not opposed to any of those thing. Whether the new instance goes above/below, I’ll get used to either, especially since the completed instance will auto-disappear, at least if the
is:complete filter is on. I was suggesting an exact copy of the most recently completed instance as probably the easiest way to code this and make it happen, but since I’m not a developer, maybe it doesn’t matter. It just sounds more complicated to have a “master” recurring task that generates all future ones. And as you mention, how would you change (or delete) the original if you needed to?
Perhaps it comes down to how we use our recurring tasks. For me, they are simple things like “Take recycling out to curb” or “Pay the bills”. If the task changes, it probably will change for all future instances, e.g. “Take recycling out to end of driveway”. If I need to make a one time change, I usually will just make a non-recurring task for that one time instance.
LauraH The other related “issue” here - is how are repeating items with CHILDREN handled.
This is something I would love to see in Legend! Dynalist didn’t handle repeating children very well, so I had to do some contortionist workarounds when there were multiple steps involved in a repeating task. It looks like Todoist has a lot of power there which would be great. But if that would delay just the (hopefully) simple addition of showing completed instances, then I’d vote to add that ASAP and wait on the repeating children.