I wanted to explain why, and discuss some things that I learned about GTD systems in the process.

But in the end, I had some issues with todo.txt that made me rethink my choice, and I have decided to go back to using ToDoist. So I used todo.txt all summer long and my initial impressions of it were very positive.

While it's not good to tinker with a GTD system that works - because you end up spending time thinking about the sytem itself rather than using the system to Get Things Done - I had a light summer, and so if I were going to experiment, this would be the time. So I switched to a purely text-based system using the todo.txt format that uses only plain text files. Briefly: My setup up to that point was to use ToDoist for all of my task lists, but I was beginning to be concerned about the control and flexibility that a proprietary system provided. You would no longer have to worry about autocomplete if you take that approach.Back in July, I reported on a switch I was making in the tools I use to implement Getting Things Done.

Drag that imported Todoist task to your calendar.

Import the Todoist task you want to work on as a task into Sunsama.

An alternative would be to not use Todoist (or it's Google calendar integration) to schedule your tasks to your calendar, and instead use Sunsama to schedule your tasks to your calendar directly: This workflow above is considered an anti-pattern in Sunsama, since Sunsama treats any event that originates from your calendar as a 'meeting' rather than a 'task'.

Import the calendar event as a task in Sunsama.

Use Todoist to create an event on your Google calendar.

If you are using Todoist's popular Google calendar integration, you'll run into this issue when you do the following: This happens for any task that comes from the calendar. When tasks originate from the calendar and are added to the task list, they will auto-complete when the end time passes.

Use Notion as your backlog via task export.

Use Trello as your backlog via task export.

Todoist google calendar