https://github.com/akramer/NextAction

A more GTD-like workflow for Todoist. Uses the REST API to add and remove a @next_action label from tasks.
https://github.com/akramer/NextAction

Last synced: about 2 months ago
JSON representation

A more GTD-like workflow for Todoist. Uses the REST API to add and remove a @next_action label from tasks.

• Host: GitHub
• URL: https://github.com/akramer/NextAction
• Owner: akramer
• License: mit
• Archived: true
• Created: 2014-03-10T03:55:47.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2016-03-23T14:42:29.000Z (over 8 years ago)
• Last Synced: 2024-04-06T21:38:50.058Z (6 months ago)
• Language: Python
• Size: 19.5 KB
• Stars: 43
• Watchers: 17
• Forks: 74
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# This code here no longer works - the torch is now being carried by @nikdoof and an up-to-date repository is located here: [https://github.com/nikdoof/NextAction](https://github.com/nikdoof/NextAction)

NextAction

==========

A more GTD-like workflow for Todoist. Uses the REST API to add and remove a `@next_action` label from tasks.

This program looks at every list in your Todoist account.

Any list that ends with `--` or `=` is treated specially, and processed by NextAction.

Note that NextAction requires Todoist Premium to function properly, as labels are a premium feature.

Activating NextAction

======

Sequential list processing

------

If a list ends with `--`, the top level of tasks will be treated as a priority queue and the most important will be labeled `@next_action`.

Importance is determined by:

 1. Priority

 2. Due date

 3. Order in the list

`@next_action` waterfalls into indented regions. If the top level task that is selected to receive the `@next_action` label has subtasks, the same algorithm is used. The `@next_action` label is only applied to one task.

Parallel list processing

------

If a list name ends with `=`, the top level of tasks will be treated as parallel `@next_action`s.

The waterfall processing will be applied the same way as sequential lists - every parent task will be treated as sequential. This can be overridden by appending `=` to the name of the parent task.