Okay, I finally had a chance to put the new sub-task system through its paces on a real project this week, and I have to say... I'm impressed.
The old implementation always felt a bit like an afterthought—just a way to nest items without much utility. Now, it actually feels like a proper breakdown structure. Being able to assign different statuses to sub-tasks independently of the parent card is a game-changer for tracking progress on complex items. Before, our "Develop API endpoint" card would just sit as "In Progress" while the design, backend, and testing phases all happened sequentially. Now we can see the actual moving parts.
What really won me over, though, is how they've handled the visual hierarchy and the summary progress bar on the parent card. It's clean, it's informative, and it doesn't add clutter. The documentation update was also spot on, with clear examples of how to use sub-tasks for different workflows like bug triage or content approval.
Is it finally useful? Absolutely. It feels like a thoughtful, integrated feature now, not just a checkbox. Has anyone else tried it with a team workflow yet? I'm curious how it's holding up under heavier use.
good docs save lives