Here's my thinking around what minimal looks like for the tasks redesign into swim lanes.
We will have just four lists per project: Inbox, Backlog, In Progress, Done.
Tasks only show the title, number, type, and inserted-at date
The list is a TaskList which belongs to Project has many Tasks
The TaskLists within the project are ordered from left to right by position integers ascending
Task belongs to a TaskList and also has a position, and is ordered from top to bottom by position descending
You can drag a task between lists horizontally and between other tasks vertically, which will update the position of the task and insert that task at the specified position
Newly created tasks will automatically go to the top of the Inbox task list
We are leaving out the following for now, which may be added on later as small, iterative experiments:
Add, delete, rename, or reorder lists in a project
Add, change, remove, and view an assigned user for a task
Add, remove, and view a skill for a task
Add, remove, and view GitHub repositories for a task
Load a subset of tasks per TaskList and load more as you scroll
Filter tasks by type
Filter out closed tasks
Display an alert on the task card when a description is missing
See the total number of tasks in a task list in that task list's header
Quickly see whether a task has been updated since you last viewed that task
Collapse the horizontal width of the task list column
Here's my thinking around what minimal looks like for the tasks redesign into swim lanes.
title
,number
,type
, andinserted-at
dateTaskList
which belongs toProject
has manyTask
sTaskList
s within the project are ordered from left to right byposition
integers ascendingTask
belongs to aTaskList
and also has aposition
, and is ordered from top to bottom byposition
descendingInbox
task listWe are leaving out the following for now, which may be added on later as small, iterative experiments:
TaskList
and load more as you scroll