Destroyed Kanban Borard (markdown)

Nathan Gray 2020-10-08 10:09:14 -06:00
parent ab305fb026
commit 41b5fe8336

@ -1,29 +0,0 @@
# Kanban planning
* EPL
* Kanban boards can have their own ACL over all
* Use projectmanager datasource as a common base
* If tied to something else (a certain project, tracker queue) it stays up to date and we put new entries in a configured column
* Boards do not _have_ to be tied to something, and can be completely arbitrary
* Entries come from other apps, and each entry is in a column
## Columns
* Configurable columns with no pre-defined meaning, just name
* Per column config, ACL, allowed apps
* Each entry has a kanban-specific sort order, with no external meaning
## Relationships
* Moving entries between columns can mean things. Eg:
** Moving from "unassigned" column to "assigned" column asks for the user, and changes the entry appropriately.
* Changing columns can have multiple effects - Moving to another column could change Assigned, status open, 10% done, etc.
* Keep entries in kanban up to date using Link change hook
* Entries can be filtered / restricted from being moved to a column, depending on how the column is configured. Eg:
## Actions
* Offer to all / supported applications
** Add to Kanban (list of top / x boards with edit rights)
## Dev steps
1. Start with just a basic board, some templates for different datasource types
2. Conditions, Relationships & moving columns & actions