![]() ![]() Now that we can see the problem statements, I need a list of requirements for my next program or platform in order to mitigate the original pain points. ![]() The system was overwhelmingly overcomplicated and I needed a way to distinguish between notes and tasks. Everything got disorganized whenever I got excited about something new and needed a place to just dump information and inspiration, but would not necessarily fit into a task card. Todoist is a checkbox/checklist oriented system (as opposed to cards/kanban with Trello or Jira) so all of my notes were just being treated like checkboxes. I had highly complex criteria in terms of where to keep each task in which column of my boards, and not being able to link specific tasks to other related tasks But I'll have to test that theory once the update arrives. I had so many lists broken up into all of my micro and niche work/personal/business projects Alternatively, once the native Google Calendar sync is made available (rumored next week), you can try to use a 2-way sync between Todoist and Google Calendar in conjunction with the Notion and Google Calendar integrationwith Google Calendar being the bridge. However, after looking at the over 300 outstanding “to do” tasks and cards on my platform, I was beginning to feel frustrated at the unnecessary complexity of my self-imposed system. I use it to prioritize tasks, collect inspiration, and aggregate information I need for my job, clients, general life stuff, and all of my other fun projects.įor a long time, I wanted to have one major program/app to house all of my projects/to-dos, etcetera. The problem I'm having is that I'm trying to make a separate scenario that will complete a todoist task when a database item checkbox has been checked. For the past 8 years, I have been using Todoist as my main application to track everything in my life. I already have a synced database from todoist to notion for the most part using a different scenario (syncs over the task name, priority, and project). ![]()
0 Comments
Leave a Reply. |