Today's state of the code, has next actions determined by due date. While this works for most tasks just fine, a subset of tasks are continually chosen as next_action when a more appropriate tasks could be selected.
For example, if you have a task that takes you 10 minutes to complete but you do that task everday, on the day that task is due, it should be the next action. But once you complete that task and tomorrow's task is created, it only makes sense to mark that task as next_action if there are no other tasks in the project.
Ideally, an estimate or start date tag indicating the number of days before the task could be started would be helpful.
Another example is, taking out the trash. I have a task in my house project that is recurring for every Thursday. I can only take the trash out on Thursday but since I run that project kanban style for everything else, it's always the next_action because of the due date.
Today's state of the code, has next actions determined by due date. While this works for most tasks just fine, a subset of tasks are continually chosen as next_action when a more appropriate tasks could be selected.
For example, if you have a task that takes you 10 minutes to complete but you do that task everday, on the day that task is due, it should be the next action. But once you complete that task and tomorrow's task is created, it only makes sense to mark that task as next_action if there are no other tasks in the project.
Ideally, an estimate or start date tag indicating the number of days before the task could be started would be helpful.
Another example is, taking out the trash. I have a task in my house project that is recurring for every Thursday. I can only take the trash out on Thursday but since I run that project kanban style for everything else, it's always the next_action because of the due date.