Create kanban-style view

[bobwhitelock]

Dragging tasks between columns should update them, either complete/incomplete or contexts.

Related: #94, #2

Columns to use should be configurable, via #122

[bobwhitelock]

Could use https://github.com/lourenci/react-kanban or https://github.com/rcdexta/react-trello (may be others)

[bobwhitelock]

Could also place configurable limits on number of tasks in each column, to limit WIP/tasks in ready, if set will warn if exceed these limits when create/view all tasks (can't make an error as tasks can be created from other sources, and might sometimes want to temporarily exceed)

[bobwhitelock]

Dragging tasks to update them is probably a nice-to-have, not needed for MVP, can always just edit directly to update

[bobwhitelock]

A few thoughts from notes on https://www.amazon.co.uk/Personal-Kanban-Mapping-Work-Navigating-ebook/dp/B004R1Q642 + thinking about this generally:

Misc

Feedback when moving tasks between columns (in particular to done) is key, as a reward and to make you note this transition and any data points on this, have some kind of animation when do this - related: #72

"Personal Kanban has only two rules: Visualize your work and Limit your work-in-progress." - initial visualization should happen just from a kanban board, ability to place limits on each column, with warning when exceeded, should help limit WIP

• how will things work when two columns are valid for a task? Could show in both, but maybe with a warning? Indicate that this task is in multiple places by showing a visual link between them on hover?

Possibly regular recurring tasks should appear in different section on boards, to avoid overwhelming other tasks?

Initial boards

Initial kanban boards it would be useful to have (and so should make these possible to configure, if minimally featured, early on)

standard workflow board (most important):

• backlog (tasks in backlog.todo)
• ready (tasks not in another column in next_actions.todo; limit on this might be useful; following columns also in this file unless indicated otherwise)
• today (tasks tagged @today)
• doing (tasks tagged @doing; limit on this would be useful)
• blocked (tasks tagged @blocked; limit on this would be useful)
• done (tasks in done.todo)
  • maybe only show some recent tasks here, at least without clicking to load more, otherwise will be thousands of items which could be bad for performance and useless
• have some way to have tasks to retro independent of "done", maybe another file tasks are sent to on completion before being moved to done.todo, or a tag that is added to things in done.todo and then removed once retro-ed

projects and contexts boards

• column per project/context respectively, maybe for both next_actions.todo and backlog.todo, created dynamically so don't need to keep changing configuration
• also all ready tasks in the backlog case, and maybe @today and @doing, so can drag things into these states

week planning

• columns for @yesterday, @today, @tomorrow, maybe each day of the week, maybe due soon
• also other columns as in previous section?

[bobwhitelock]

Need to decide MVP features from above, log rest to come back to. Maybe just do stuff to create minimal standard workspace board:

• can define kanban views in config file (Have config file for configuring all settings #122)
• will be shown as separate view in own tab, like file-based views
• can define columns when doing this, initial definitions needed:
  • tasks in file with single given context
  • other tasks in file (in some cases will be all tasks except those in another context-specific column, in other cases this will be every task in a file since that file is not used in any other columns)
• limit tasks shown in each column to some number that is more than usually sufficient but not everything - e.g. 100 - no way to load more initially
• no drag and drop initially, all edits via usual buttons on each card
• no WIP limits
• maybe could have buttons to add task to each column, or just do this via normal process in each grid view