Motivation
The current Project Hub is optimized for viewing projects and tasks, but it’s not strong as a management surface once a user has many projects + recurring automation.
As usage grows, a few pain points show up:
- Triggers are invisible in the hub
- There’s no trigger count shown per project/task.
- There’s no direct way to manage triggers from the hub, so users have to click into projects to understand automation coverage.
The table list doesn’t scale for different mental models
- Users sometimes think in projects (what’s happening in each project),
- sometimes in tasks (what’s currently running / stuck),
- and sometimes in triggers (what automations exist and what they run).
- Right now there’s only one flat table view, so users can’t switch perspective.
Running vs finished visibility is unclear
- The current icon/status change is subtle.
- It’s not obvious which projects are actively running vs already finished.
Hub lacks core “management” actions
- No multi-select / bulk actions.
- No pinning for important projects.
- Sorting/ordering is limited.
- Actions are not standardized or easily accessible from one place.
As a result, users who run many automation-heavy projects must:
- Click into projects repeatedly to check trigger coverage.
- Struggle to understand “what’s running right now” vs “what’s already done.”
- Manually manage projects one-by-one without bulk operations.
- Lose time finding active / important projects without pin + sort.
Solution
Proposed solution (The Design will be provided next week for whom would like to contribute)
Refactor Project Hub into a management-first hub with:
- Trigger visibility + entry-point management
- A dynamic multi-view layout (Projects / Tasks / Triggers)
- Stronger status clarity for running vs finished
- Core management UX: multi-select, pin, sort, and standard action dropdown
- Trigger count display + management entry point
- Show trigger count at hub-level (at minimum in Projects view).
- Triggers are first-class in hub navigation (via Triggers view).
- From the hub, users can quickly reach trigger details/management (enable/disable/edit) without needing to open each project.
- Dynamic multi-view hub (replaces single table mental model)
Convert the current table list into a dynamic display that supports:
- Projects view: manage projects + see status + trigger counts
- Tasks view: manage tasks across projects (status, recent activity)
- Triggers view: manage triggers across projects (what runs, where, status)
Users can switch views without leaving Project Hub.
- Clear visibility for running vs finished
- Make running vs finished states obvious (not just subtle icon change).
- Improve the status indicator (label/chip + optionally last run/updated metadata).
- Support quick scanning to answer: “What’s active right now?”
- Multi-select + bulk actions
- Support selecting multiple projects (and ideally tasks/triggers in their views).
- Enable bulk actions like:
- Delete
- Pin / Unpin
- Pin projects
- Allow pin/unpin from row/card actions and/or inline.
- Pinned projects appear in a pinned section or top of list.
- Pin state persists per user.
- Sorting and ordering
Support sorting options (at minimum):
- Name
- Last updated
- Status (running/finished)
- Trigger count
Sort state persists per view.
- Standard item action dropdown
Add a consistent dropdown on each item (project/task/trigger where relevant):
- Open
- Duplicate
- Pin / Unpin
- Copy link
- Share
- Rename
- Delete
- Show action history
Alternatives
No response
Additional context
No response
Motivation
The current Project Hub is optimized for viewing projects and tasks, but it’s not strong as a management surface once a user has many projects + recurring automation.
As usage grows, a few pain points show up:
The table list doesn’t scale for different mental models
Running vs finished visibility is unclear
Hub lacks core “management” actions
As a result, users who run many automation-heavy projects must:
Solution
Proposed solution (The Design will be provided next week for whom would like to contribute)
Refactor Project Hub into a management-first hub with:
Convert the current table list into a dynamic display that supports:
Users can switch views without leaving Project Hub.
Support sorting options (at minimum):
Sort state persists per view.
Add a consistent dropdown on each item (project/task/trigger where relevant):
Alternatives
No response
Additional context
No response