3 ms·
I really wish TW finally got around to implementing the ideas to improve recurrences here: https://taskwarrior.org/docs/design/recurrence.html https://taskwarr
by BaseballPhysics 4y ago
I really wish TW finally got around to implementing the ideas to improve recurrences here:
https://taskwarrior.org/docs/design/recurrence.html https://taskwarrior.org/docs/design/recurrence.html
Basic things like "do a thing on the first Monday of every month" just aren't possible, and other kinds of recurring tasks (e.g. do something weekly) work strangely.
These limitations rule it out for a lot of my day to day use cases, which is a shame because otherwise there's a lot to like.
- jareds 4y agoThe recurrence is the one reason I don't use Taskwarrior. I use topydo instead because recurrence works better with it. The project may be dead but as long as I can get a few years out of it I'll switch task lists when it finally totally breaks.
- deleted 4y ago[deleted]
- gen220 4y agoThis might not work for you, but I've found that "recurring" tasks and the never-ending stream of "one-off" tasks are best managed in separate applications. I use a kanban-style thing for managing one-off's, which I use to "fill-in" my free time, and a calendar/reminder-style thing that I use to schedule recurring events. It's possible to set up syncing between the two, but I haven't found it necessary. At first, I tried to put recurring things in the kanban-style app. They would fester and quickly/irreparably get out sync with reality. I also tried putting one-off things in the calendar/reminder-style things, but managing a backlog in such an application is usually a nightmare. I've experimented with TW in the past. I really enjoyed the productivity aspect. Ultimately, I discovered that portability (i.e. a web interface) was more important than efficiency, and crawled back to the kanban-style thing.