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
9 Comments
I'm partial to Things 3's handling of recurring tasks. You can specify recurrence based strictly on the date, regardless of the state of the previous instantiation, as described above. OR it can be based off the completion date of the existing item—the next day, or 5 days or 3 weeks after the current item is marked done.
It is worth mentioning that this is possible to build now using the Command Node 'Insert relative date'. Like RJ Nestor has done (a demo of it in use here): https://www.youtube.com/watch?v=6ikLbN0JoeY
Personally I think the gold-standard for recurring tasks is TickTick, because it allows you to set the recurrence based on either due date or completion date. Setting it to completion date is useful for things like house chores, or anything that needs to happen on a fixed frequency rather than a fixed date.
The recurring task settings in Amazing Marvin are probably the most comprehensive I've ever seen.
I have already used up my two votes for this month, but this is also an issue (for me) I desperately would like to see solved.
This is too complicated and fish back In order to realize such a basic function .it is a bit worthless
I have to agree with other commenters: building this out manually is a pain and far from an "elegant solution" from a UX perspective. This should come standard and I am sure you and the team are aware of that. I get that people in the Tana environment build personal businesses around selling such solutions to other Tana users, but once you pay for the software, things look differently.
The homepages claims Tana to be "The everything OS", but only if you literally build everything yourself? It's supposed to be "A game-changer for project management", but only if you spend literal hours (plural) to configure it (and then spend many more to maintain it)?
I already used up my votes, but I will come back next month.
Ferramenta incrível que simplifica significativamente a gestão de datas e eventos em aplicações e melhor jogo. A implementação deste campo permite aos utilizadores configurar facilmente eventos recorrentes, como reuniões semanais ou tarefas mensais, com mínimo esforço. No contexto dos jogos, tal campo pode tornar-se um elemento-chave na criação de mecânicas de jogo dinâmicas.