Repeating Events are pretty half-assed?

Jorge

LauraH One possible work around would be to add another view / filter option that was “hide all repeating items”. In fact, this type of filter has been suggested / requested in the past and I could see many uses for!!

@LauraH This filter is already implemented by Jay. The syntax is: date:repeating in the advanced filters.
I think there should be an icon for this in the simple filter menu as well.

I totally agree with @LauraH regarding people that don’t want to see the history of the completed individual repeating items. They can currently filter them out if they don’t want to see them. However, there is another important reason why they should be there. You might want to add specific notes to each completed instance that do not apply to the repeating pattern. Especially if you are trying to use Legend for Journaling needs.

Jorge

Jerud 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.

Most organizers I’ve used manage the repeating series as based on the next active event, and not on the first ever executed event. Thus the completed events remain as history and become unrelated to the recurring series. If you want to change the recurring series you select the series which is pointing to the next due date and the completed ones remain untouched. That’s why I believe the series should be handled as an object itself, but as soon as you complete an event, a copy of the event with the current due date should be generated and marked as complete, and the series rescheduled to the next iteration.

Jorge

LauraH The other related “issue” here - is how are repeating items with CHILDREN handled.
In my experience, Toodoist has the clearest and most helpful options around this. See their documentation here: https://www.toodledo.com/info/subtasks.php#slider-7

I agree that this behavior is the most general one and should be the preferred one as it covers all the cases I can think of and that people have expressed before.

Having said that, just as the others, I think that the first thing to imlement soon should be the saving of the completed items, and then later Jay can deal with the children.

Jorge

Jerud I recently started using entirely “local” events instead of syncing to Gcal. Although I miss having a color-coded Calendar,

I have created a separate feature request for this sort of thing. https://forum.legendapp.com/d/609-color-coding-the-calendar-items

LauraH

Currently - if you complete a repeating item, the item schedules itself for the next instance; but there is no record of previous instances. No record of when the tasks were completed.
I would really appreciate having that record.

To have a “habit tracker”, a record of how often I’ve completed (or missed) the various habits / babysteps / routines I’m working toward.
As a “Go Me” list. Most days I’m an at home mom; and big chunks of my work involve repeating/recurring chores. I would really like to look back on my “Completed” list for the day and see the chores included! A big help on days when I mentally feel like the day was a “waste” to be able to see a list of things I did accomplish.

webalstrom

Jorge Well, that was confusing! Before I read your post that the threads had been merged, I thought I was in a time warp. But makes sense to keep these things together.

A question about voting on things. I have clicked the “thumbs up” on Jerud’s original post in this thread. I also clicked for LauraH’s original post in the merged thread. Just to be safe, I clicked for Jorge’s post about merging and upvoting. What is the proper way to upvote topics you think are important and want Jay to focus his attention on? Is it the original post even if the discussion later on brings out points you think need attention? Or should you vote for each of the posts? It would make more sense if the entire topic had just one place to vote for it instead of each post within the topic. I know this is how our forum platform works, but knowing where to vote would be helpful. In Jay’s intro for the forum, he just says vote, but not how or where!

webalstrom

I agree with LauraH on this. It would be nice to have a record of what has been done for repeating tasks. Sometimes it’s just a matter of “did I really do that this week/month/year?” Having the crossed-off completed task to confirm this would be helpful. The completed copy should have a created (and modified) date of when it was completed while the new instance, with the updated due date, carries the original created date but indicates it was modified when it was completed (just like it does currently).

LauraH

@webalstrom - To help track of the relative desire for various feature requests; could you please up vote this (the arrow button) to indicate your desire for this feature also? That helps Jay to have a way to see what feature requests are most desired.

webalstrom

@LauraH Just added my vote. Thanks for the reminder to do this!

Jorge

I think we were discussing this on a separate thread. @LauraH I merged your request with @Jerud ’s thread to try to give it more relevancy. @webalstrom maybe you could upvote the merged thread as well?

LauraH

webalstrom
The only votes that are visible on the “Main” forum page are those applied to the FIRST post in the chain. You can also upvote it on that main page without opening the thread.
I suspect that is the most helpful place to upvote?

Jorge

webalstrom Personally I always got confused about that so what I do is just upvote in the main list of topics. The blue arrow indicates you upvoted something, if it is grey it means you haven’t upvoted that item.

webalstrom

LauraH, this is helpful to know! I did upvote on the first post of this topic (as well as others I think need attention), so I did it in the right place.

Jorge

Recurring items being marked as complete are not being handled correctly.

Given an item set to recur every day at 11:59pm from 4/25 for 3 times , intended to repeat daily for 3 consecutive days (an medicine I had to take).
When every day I have marked the daily item as complete, it should have yielded the pattern to fully complete have been done by 4/27.
Then, however, today (4/27) when I checked it it is still open and showing the recurring pattern as of today

So it would seem to me that it is just changing the start date of the recurring patter every time I check the daily item as complete.

Jorge

Not sure if the problem is with how recurring dates are being handled or the grouping functionality.

Given a recurring transaction that occurs every month.
When a pane is displayed as Outline grouped by Agenda, Agenda mode: All
The transaction (which is next due on June 4, and today being May 3) shows up as overdue, which is incorrect as the transaction is due one month from today.

My guess is that the interpreation of dates is being incorrectly managed between the traditional international date format and the typical US date format.

June 4 in US format is 6/4/2023
June 4 in international format is 2023/6/4
June 4 in DMY format (which is the one I have Legend set to) is 4/6/2023

Today is May 3 (5/3/2023, or ⅗/2023 or 2023/5/3)

If the app is reading 4/6/2023 and interperting in US date format it’s thinking that it was due April 6 and that could be why it’s displaying it as overdue.

Jerud

Jorge I’ve seen something similar to this date issue. I can’t remember the particulars of it, but I occasionally see dates render in the “wrong” format vs. my date settings. It may indeed be on repeaters. I think I was editing the date and my interaction seemed to alter the format. It got weird and I ended up fully clearing the date and reapplying.

I’ve got hundreds of “nit picking” bugs like this documented already, but I never get around to posting them (because why) so have mostly stopped writing them down at all.

It does seem that there are some corners of the app where custom date formats weren’t fully implemented.

LauraH

This is an older thread; but I keep wishing for the functionality discussed here.

I want a RECORD of my completed recurring events. I don’t just want the date to change, I want to see it in my completed list. I want the “created” date of the new event to reset. I want to be able to see what I’ve completed, track habits, etc. with recurring events.

Jorge

LauraH I agree, the proper functionality should be:
Given a recurring task
When you mark it complete for the current date
Then the due date should reset to the next occurrence and a completed (non recurrent) event should be created as a child of the recurring task. This way when you open the task you can see the list of all past completed events.

LauraH

Jorge I’d be very happy with the implementation you describe. I would also be happy if it simply generated the next event at the same level as the parent. Either functionality would be fine for me.

Key things I want are to have a record of completing recurring events, and have the next event have an appropriate created date.

Jerud

Jorge A decent suggestion but one must be careful to generalize it. Since dates can be applied to any item, at any level of the Outline, a Repeater could be on a Parent item (or even a big branch with sub-parents). Nearly all my repeaters are, in fact, parents. So if the history of past instances goes under it as children, they would get mixed-in with the item’s actual children. At which point they would look like they should get duplicated into the next instance along with the repeaters’ bona fide children. This would require exceptions and special handling to avoid issues.

Also, for Systems that place import on the depth of an item in the Outline, storing historical instances as children would be an issue.

TL;DR: the “history” should be created immediately below the item in question and at the same outline level.

It would be nice if there were a way to show/hide the history of a repeater on a per-item basis…but a filter for (-is:complete has:date) would get that job done – though it’d operate on the whole Pane and also hide completed non-repeaters, so isn’t perfect.

« Previous Page