Liam White

Explain the problem as you see it

It is possible but cumbersome and somewhat manual to model something like a recurring task/event in Tana.

Why is this a problem for you?

Instead of using the cumbersome method its easier for me to keep all my recurring tasks in Todoist and have written a Tana paste script to read and move them over every morning.

Suggest a solution

Either an extension of the date field or a new field, attached to DONE/NOT DONE that would change the date to the next occurrence when DONE is checked (and then uncheck DONE).

I really think Todoist's Natural Language style entry is the gold standard for UX on this type of thing:

• every 5 days
• every week day
• monthly on the 1st