
Last updated: May 29, 2026
TL;DR: Quire's Nested Kanban Board keeps subtasks grouped under their parent task on the board instead of scattering them as loose cards. The feature is called Task Bundle. Toggle it on to preserve your hierarchy in card view, toggle it off for a flat board. Available on Professional and higher plans.
For a long time, Quire users asked for one thing over and over: let the nested task list meet the Kanban Board. You'd build a beautiful tree of tasks in the list, switch to the board to run the work, and watch the structure flatten into a pile of cards. The relationships you'd carefully set up just vanished from view. Now they don't.
If you've touched agile project management, you already know Kanban. A traditional board visualizes a project as cards in columns, where each column is a stage and you drag cards rightward as work moves along. It's simple, visual, and it works.
The discipline underneath it is older than the software. According to David J. Anderson's book Kanban, which adapted the method from Toyota's factory floor for knowledge work, the habit that actually makes a board useful is limiting how much sits in progress at once, so the eye can follow the flow. That works well when every card is a peer.
It breaks down the moment your work has parents and children. A flat board has no way to show that "write API docs" and "review API docs" both belong under "API launch." They float as three unrelated cards, and the context you built in the list is gone.
Quire is known for its infinite nested task list, which gives a project far more context than a flat to-do list ever could. The Nested Kanban Board carries that same hierarchy onto the board, so switching views no longer means losing the shape of your project.
Task Bundle is the toggle that does the work. Turn it on and Quire groups subtasks under their parent task as a single "bundle," so you never lose track of which task belongs to which.
Task Bundle is available on the Professional, Premium, and Enterprise plans. The flat Kanban Board itself is free on every plan. Full details are on the pricing page.

Toggle on the Task Bundle option in the Board icon dropdown menu, and every task regroups inside its own node. Instead of detaching subtasks from their parents, the board now shows the relationships between them. You keep working exactly the way you would in the List view, just with cards.
When you drag a task bundle to another column, the whole bundle moves together. Only the first-level task picks up the new column property by default. To apply it to the entire bundle, hold the Alt key while you drag.
When you're done with the nested view, toggle Task Bundle off and your board regroups into a flat layout. Nothing about your data changes underneath; only the way the board renders it.
Most PM tools have a board. The interesting question is what happens to subtasks when you switch to it. Here's how the common tools handle hierarchy on a board.
| Tool | Subtasks shown on board | Hierarchy preserved | How it's handled |
|---|---|---|---|
| Quire | Yes, nested under parent | Yes, via Task Bundle | Parent and subtasks move as one bundle |
| Asana | Generally not on board | No | Subtasks live in the task pane, not the board |
| Trello | No native nesting | No | Checklists stand in for subtasks |
| Monday | Subitems hidden under parent | Partial | Subitems expand inside an item, not as cards |
| ClickUp | Behind an expand toggle | Partial | Subtasks shown via a toggle, not bundled |
The pattern: subtasks are common, but showing them attached to their parent on the board is rare. Most tools either hide subtasks on the board or flatten them into checklists. Quire's Task Bundle is the unusual row here, and it's the reason switching to the board doesn't cost you the structure you built.
Task Bundle isn't always the right call. Sometimes a flat board is genuinely better.
For work where each task stands on its own and its individual status is what matters, the flat Quire Kanban Board is the cleaner read. A content pipeline where every article moves through the same stages, or a support queue where each ticket is independent, doesn't gain much from bundling. The parent-child relationship just isn't the important thing there.
Use Task Bundle when the work is a real tree, where a subtask only makes sense next to its parent. Use a flat board when the work is a set of peers marching through the same stages. The toggle exists precisely so you don't have to commit to one forever. (If you want the longer argument for keeping hierarchy across every view, we made it in the Nested Concept post.)
Open a project that has real subtasks, switch to the Board view, and toggle on Task Bundle. The difference usually clicks within the first minute, because you can finally see which cards belong together instead of guessing. For the full walkthrough, visit the Quire Guide.
Let us know if you love bundling your task list as much as we do. Share your thoughts in the comments or tweet us at @quire_io.
A board that keeps subtasks grouped under their parent task instead of scattering them as loose cards. Quire calls the feature Task Bundle.
Open the Board view, click the Board icon dropdown, and toggle Task Bundle on. Toggle it off to return to a flat board.
Professional, Premium, and Enterprise. The flat Kanban Board is free on every plan.
The whole bundle moves together, and only the parent takes the new property unless you hold Alt to apply it to every task in the bundle.
When each task is independent and its own status matters more than its parent, like a support queue or a single-stage pipeline.