[Feat] Add shared task board view - #1504
Conversation
| <TooltipContent>{activityDate.toLocaleString()}</TooltipContent> | ||
| </Tooltip> | ||
| </div> | ||
| <div className="text-base font-semibold leading-snug -mt-1"> |
There was a problem hiding this comment.
This rewrite drops the work-type and source badges from every board card. getTaskWorkType and the newly fetched surface value are now unused, so users lose the context the board is intended to show. Please render those badges again or remove the now-dead data path.
| </Button> | ||
| </div> | ||
| )} | ||
| <div className="flex items-center rounded-lg border border-border p-0.5"> |
There was a problem hiding this comment.
The board-only Mine/Everyone controls were removed in this refactor. The remaining generic user filter can select arbitrary users and automations, but it no longer gives board users the promised one-click team scope switch. Please restore the scoped toggle (or change the requested board behavior).
There was a problem hiding this comment.
Let's keep this change as is for now to avoid the duplicated user selectors. Happy to revisit after some use and feedback.

What changed
Adds a URL-backed board view alongside the existing task list with automatic Active, Needs input, Blocked / failed, and Done columns. The board includes Mine/Everyone scope controls, work-type and source badges, creator and participant avatars, activity timestamps, workspace and pull-request context, and a six-task Done shelf.
The task-list query now returns the source, goal blocker state, and distinct linked human participants needed by the board. Focused component and classification coverage protects lifecycle precedence, responsive content, metadata, and Done overflow.
Why this change was made
The current task page is optimized as history rather than a shared operational workspace. Teams need a quick view of what is active, waiting on them, blocked, or recently completed without introducing a second manual status system.
Impact
Teams can switch between list and board views while keeping existing filtering and pagination behavior. Board state is derived from durable task, goal, and run-phase data; completed work stays bounded instead of accumulating indefinitely. The checked-in Storybook stories provide representative desktop and mobile demos because the local product route is currently gated by mandatory inference-provider setup.
Screenshots
Desktop Storybook fallback
Mobile Storybook fallback