I think this would be an amazing feature for people trying to build routines and people who are systems-oriented looking to create recurring tasks/projects on a daily/weekly/monthly cadence. The #1 reason I left Notion was because I had to use Integromat/Make to create recurring tasks. Everything else was great (and I think AnyType has the potential to be even greater), but I’m so reliant on whatever task manager I’m using and there are so many things that happen for me on a recurring basis that I just forget. If AnyTime had an intuitive way to create recurring tasks, that would be absolutely game-changing!!
I think this is a great idea to have the option of recurring/repeating tasks for appointments for example with a certain frequency of occurrence. It’ll be great to have the option not only of the traditional monthly weekly daily but also custom frequency.
Does anyone know what the status of this feature request is?
Alternative idea, instead of having an object automatically created on a schedule (like notion’s recurring templates), allow dates to have a “repeating” option. This would be more similar to how e.g. Google Calendar handles repeating events/tasks, and is imo more anytype-ish and less notion-clone-wannabe-ish ;-). Though I can see value in both methods, and they wouldn’t be mutually exclusive.
Can you please describe your particular use case for this feature please. More robust and clear will be the description more user centric and helpful will be the implementation. And also it will help us to understand this particular need better
One way to avoid generating too many objects could be to allow the “rules” to be set, but only create the actual objects once they need to be actually used/edited.
For example, for this case:
When the user requests this, Anytype doesn’t have to actually create all the objects. Instead, it adds this as a “rule” to the object list.
This means that, despite no objects having been created, all of them could still show, either within Sets or as Search results. As soon as the user clicks to enter/edit the object, then it’s actually created
Of course, I have no idea how Anytype implements objects, so maybe this isn’t viable. Just an idea.
Maybe this would be overkill for situations like the example above (there aren’t that many weeks in a year). But it would allow for rules with no expiry date (ex: 1 meeting a week forever).
Don’t forget annual and quarterly objects! This would work best with the future calendar feature, but implementing it on tasks could work, too.
Use case: bill reminders, birthdays, habit tracking, etc.
I’m thinking a reccurence rule/setting could be added for task objects. If you choose ‘once a week’, then once that task is checked off, a copy will be made and assigned for the following week.
Of course other settings need to be considered: recurrence limit, do you generate all tasks at once, assigning dates vs. generating new object only when task is completed, etc.
When creating a new Task in MS To Do you can set a Repeat option (Daily, Weekdays, weekly, Monthly, Yearly, or Custom). When you mark the Task as done, a new Task is automatically created with a new Due Date based on the recurrence configured in the Repeat option. This would ensure there is not an (endless) list of Tasks created immediately upon creating a first recurring Task (or in Anytype an Object of Type Task/Note/etc.), but only when relevant.
In the case of MS To Do, there is NO new Task created if the open Task is not marked as complete. This will be an issue in Anytype as everyone might use their own way to mark a Task done, and for certain repeating/recurring Objects, it is irrelevant to mark the Object as “Done”. Therefore, I can imagine that it is best to only actually generate the Objects that are within x iterations of the recurrence setting (either a fixed number or something dynamic, for example, only the next 4 Objects when set to daily, only next 4 when set to Weekly, only next 12 when set to Monthly, only next 4 when set to Quarterly, only next 2 if set to Yearly). I think it could be part of the “startup script” of Anytype to check upon starting whether there are new versions of the software available, and whether there are new recurring tasks that need to be created (and possibly other things that are not relevent for this feature to work).
No ETA for today. It will depend on our bigger picture strategic plans we are working on in the moment. I think timing will be more clear after public release
