The idea of this step is to review your system regularly, so you are sure, your lists are actualized and the next action was created for each task. Also add the information, when it was delegated and the deadline, so it will also appear in my calendar.

Label “delegated “- if the task will be done by the other person.

Optionally I add a label with the location or person, it’s connected with.

Label “next action “- if the task doesn’t have a specific deadline.

Specific date - if the task has a deadline.

The rest of the tasks are moved to the specific project, using also the next criteria: When my system is created, I move tasks, which can’t be done soon from inbox to incubator. So that your someday tasks won’t show up on your nextaction list.Labels are great for pulling together tasks by location, person, or type of work. When Nextaction meets a task which should be tagged currently has tag it won’t tag to that task. |-taskE // This task will be tagged also supports a tag called The logic is: | |-taskC // This task will be tagged |-taskD Parallel tasks and sequential tasks can corporate with each other seamlessly: |-taskA.

|-taskB // This task will be tagged // This task will also be tagged that you can add a filter on to make you focused. |-taskD // This task will be tagged for parallel tasks: |-taskA. |-taskB // This task will be tagged you complete taskB, it will become |-taskA: Run it by docker run -it -e NXTT_token= wooya/nextaction IntroductionĬopy-pasted from the README will auto tag current nextaction task with It also supports parallel task (with ‘-’ append) Run: git clone & cargo run -release Docker ImageĪ docker image is also available. To build the application, rust is needed. You should set environment variable NXTT_token to your Todoist token. And you can see after that the compiled docker image is only 18M which is much easier to distribute (Actually I’m considering a “nextaction as a service”, a.k.a. The rationale behind is that it should be a simple application with as less as possible dependencies, not python with lots of redundant libraries. Rather than using python, I chose to write it in Rust. Inspired by here, implementing by a polling server is a trivial but decent way. But since Todoist hasn’t provided this feature(maybe they don’t want this forever), we need to exploit the todoist api to achieve our goal.

With nextaction, one can keep really focus on things he should do, which is really nice. If you are a fan of MLO or Omnifocus, I bet you will really miss the nextaction feature if you migrate to Todoist.

Todoist next action