For me I think it depends on how your org is handling the source of truth for tasks and work. I know you can use checklists within stories and tasks to break th

For me I think it depends on how your org is handling the source of truth for tasks and work. I know you can use checklists within stories and tasks to break things down without cluttering boards with new tickets, and capturing discussions within the ticket itself helps to compartmentalize things and avoid jumping around different tools. If a story is your smallest unit of work, does one developer own a story? Or are multiple people working on it? Intuitively it feels like if multiple people are working on a single story then it feels like that should (or at least could) be broken down into subtasks (or checklist items, if you didn’t want to create new tickets) that could be split between developers, and keeping that context and discussion within that ticket, I would think, would be helpful for knowledge sharing and drawing from that discussion to feed into your longer term knowledge base docs. Just food for thought from someone who tool hops way too frequently with poor short term memory .