PRJ-158 · 2 pts
Empty states for archived boards
N4N PROJECTS · GATE 19
n4n Projects puts boards, timelines and sprints in the same place your docs, chat threads and tickets already are — cut a task from the spec, argue it out on the card, and watch the burndown fall as it ships.
Gate 19 · Productivity · boards with the next wave
PRJ-158 · 2 pts
Empty states for archived boards
PRJ-149 · 5 pts
Drag to reschedule on the timeline
PRJ-141 · 3 pts
Keyboard nav on the board
PRJ-144 · 3 pts
Burndown in the sprint header
PRJ-146 · 3 pts
Quick-add from any view
PRJ-152 · 3 pts
Sprint report export
PRJ-147 · 5 pts
Swimlanes by assignee
Burndown · sprint 14
7
pts left of 24
on trackSPECIMEN · SPRINT 14
Day nine of a ten-day sprint. The report export ships, the swimlane review clears, and the chart in the corner redraws itself — the burndown is computed from the board, never typed into it.
→7 tasks · 24 pts planned
→review rules assign themselves
→burndown redraws on every move
CAPABILITIES · MANIFEST
Board, list and timeline are the same tasks, differently arranged. Drag a card on the board and the timeline bar moves with it — nothing to sync, nothing to re-enter.
Plan a sprint in points, and the burndown redraws the moment a card reaches Done. Day nine looks like day nine — not like the graph someone tidied before the review.
Estimate, rank and slice the backlog in one pass. Priority order carries into planning, and anything cut from an epic keeps its link back to the spec it came from.
Every task carries its own thread. Decisions made in Chat pin themselves to the card they are about, so the reasoning is still there when someone asks why in October.
When a card enters Review, the rule assigns a reviewer and posts to the sprint channel. Recurring chores re-create themselves. The board does the ceremony for you.
Sprint reports show points shipped, carry-over and velocity across the last six sprints — so the next plan is based on what the team actually does, not what it hopes.
ROUTE MAP · GATE 19
A task is rarely born on the board. Three routes bring the spec, the conversation and the customer to the card — same account, same record, no exports.
n4n Chatscheduled
Chat keeps the standup async — every card has a thread, and a decision posted in the sprint channel pins itself to the task it belongs to.
n4n Docsscheduled
Docs holds the spec — link a doc to an epic and every task cut from it keeps the brief, the comments and the version history one click away.
n4n Deskboarding
Desk feeds the backlog — escalate a ticket and it lands as a triaged task with the customer thread attached, closing the loop the day it ships.
n4n Projects
GATE 19 · SHIP LOG
sample day · times local
BOARDING INFORMATION
Straight answers on status, what a sprint looks like here and how Projects will be priced when it boards.
Not yet. n4n Projects is boarding — it is in active development as part of the next wave of the fleet. The only app live today is n4n AI. Email support@n4n.io and we will tell you the moment the gate opens.
Both, on the same tasks. You can run a plain kanban board, a ranked list, a drag-to-reschedule timeline, or full sprints with point estimates, a live burndown and per-sprint velocity reports. Switching views never copies or duplicates work.
It shares one login and one balance with every n4n app. Specs in Docs link to epics, every card carries its Chat thread, and Desk tickets escalate straight into the backlog — no connectors, no exports, no glue code.
The same way as the rest of the fleet: one prepaid balance, pay for what you use, no per-seat pricing and a $0 minimum. Top up once and every n4n app draws from the same balance.
N4N PROJECTS · GATE 19 · BOARDING
n4n Projects boards with the next wave of the fleet. Leave your address and we will tell you when the doors open — or start today with n4n AI, the departure that is already live.
one login · one balance · $0 minimum