Project management for teams and workflows
Three teams, three methods, one workspace. Estimates, dependencies, checklists and sign-offs are checked by the server on every path that can move a card. Not a warning. A refusal, with the reason attached.
No card. Three teammates included.
Three refusals, quoted from the source. Same answer whether the card is dragged, bulk-edited, or moved by an automation.
This board requires estimates. Add one before moving the card into Design.
This board moves one stage at a time. You can’t skip ahead.
This card still has 2 of 5 sub-tasks unticked — finish the checklist before moving it to Done.
Backwards is always free. A card can be pulled back down the route at any time, so getting unstuck never needs permission.
A board is one reading of the work, not the work itself. The list is where you triage. The calendar shows a crunch week before it arrives.
Double-click a title to edit inline · Click a row to open
Every card has a date.
Timeline, swimlanes and the flow report read the same cards. So do drafts, tickets and hand-offs.
Support runs continuous flow. Product plans in cycles. Compliance needs controlled stages and a signature. Three boards, one workspace, the same people and history.
Continuous flow
No ceremony. A WIP limit of three keeps the middle column honest.
Two-week cycles
Points, burndown, and cycles that start and end on their own dates.
Approval flow
No skipping a stage. Sign-off freezes the card until someone signs it.
One plan, everything in it. Five days free for up to three teammates. No tier hides the gates or the reports behind an upgrade.
No card up front. If it is not carrying your team by day ten, you have lost ten days and nothing else.