I agree with a specific meaning of this. "Bug and task" is unsolvable. Those are very different things, usually existing for different levels of organising work. Yet, often they're forced into one system.
That solution sucks though: there's a bug, my own task may not may not relate directly to it, the team goal may or may not include that task specifically. I've enjoyed life more since those things got mostly separated for me.
The unit of tracking for how we think of things is some highly overloaded version of "project" which could mean project or team or org or repo or short lived event plan or anything else. Our terminology is probably wrong and it forces the way we think about the problem. It very much feels like a "everything is nail shaped" situation and we want everyone use the same model hammer. Jira, for all it's faults, does offer two or three different ways of doing work (with the recent addition of their DevSecOps thing that I haven't actually looked at).
Tasks != Bugs != Requests != Roadmaps