One Backlog, A Kanban Board
And Every View In Between
To Do
Rate-limit webhook ingest
Empty state for inbox
In Progress
Fix OAuth token refresh
In Review
Stream billing export as CSV
Event broker failover tests
Plan In The Backlog
Ship From The Board
Every view is a lens on the same work items. Change something in one and it changes everywhere.
Five Views, One Set Of Work Items
Groom the backlog, run standup from the board, scan the list and drag due dates around the calendar. Filters carry across views and live in the URL, so a filtered view can be shared as a link. Finished work moves to the archive instead of cluttering the board.
- Backlog, board, list, calendar and archive
- Filter by assignee, type, label, status and priority
- Auto-archive done items after 1, 7, 14 or 30 days
To Do
Rate-limit webhook ingest
Empty state for inbox
In Progress
Fix OAuth token refresh
In Review
Stream billing export as CSV
Event broker failover tests
A Workflow That Matches Yours
Each project has its own statuses, with a name, a color and a category, in the order you drag them. Add a column straight from the board, rename safely, and when you delete a status its items move somewhere sensible instead of vanishing.
- Custom statuses and labels per project
- Epic, story, task, bug and subtask
- Five priority levels and more than one assignee
Everything About A Ticket, On The Ticket
Subtasks, threaded comments with @mentions, attachments, time logs and linked commits sit in one panel, with an activity history that shows the old and new value when status, priority, dates, assignees or labels change.
- Threaded comments with @mentions and reactions
- Attachments, time logs and linked commits
- Activity history with before and after values
Stream the billing export as CSV
Write the CSV streamer
Hash each export row
Rate-limit per tenant
Comments
4
Commits
3
Logged
6h 30m
@Alex can we ship the hashing first? QA is waiting on it.
And The Small Things
That Add Up
Private drafts
Shape a work item privately, then promote it to the board when it's ready.
Quick create
Type a title, press ↵ and keep going. Items can also be created right in a board column or on the calendar.
Keyboard first
⌘K to jump anywhere, J and K to step through open work items, M to comment.
Work-item keys
Every item gets a project key like NBX-218, which also links commits that mention it.
Due-today reminders
Assignees and the reporter get a reminder on the day a work item is due.
Noa reads the board
Ask what's stuck or who owns the overdue work; Noa answers and names the work items by key.
Questions, answered
Yes. Every project has a board view with a column for each status, and you can add a column straight from the board. Cards drag between columns, and the same work items also appear in the backlog, list and calendar views.
Yes. The backlog holds the work that isn't in a sprint yet. You can select items in bulk and move them into a sprint, change their status or priority, or create a new sprint from the selection. Noa can also propose backlog items from a spec, PRD or CSV.
Statuses, yes: each project has its own, with a name, color and category, in any order. Work items use five types: epic, story, task, bug and subtask.
Yes. The list groups work items by status, and the calendar shows them by month or week, with drag to reschedule. Both use the same filters as the board and backlog.
On any finished column you can archive items automatically after 1, 7, 14 or 30 days. They move to the archive view instead of crowding the board, and moving an item back out of the column brings it back.