I used it a few jobs back. By management decree we were supposed to be using Asana for everything, but it was extremely painful not being able to format snippet

I used it a few jobs back. By management decree we were supposed to be using Asana for everything, but it was extremely painful not being able to format snippets of code or cross-reference code or commits. Maybe Asana can do those things now, but luckily we managed to convince them to let us use GitHub issues. It was a small company with a single small dev team, so we didn’t really feel a want for any JIRA-like features. But after that I’ve only worked for big multi-team JIRA shops. But I’m not sure if the whole JIRA bureaucracy is actually necessary or even all that helpful at scale. It’s ostensibly a solution to the velocity problem, but even with a perfect burndown chart we tend to spend an order of magnitude more time than anticipated, only to discover in the end that we built the wrong thing. I suspect that the real reason is that the devs and domain experts consistently fail to communicate, and when they try they rarely even use the same language to describe the same domain concepts. I think that if we can solve the domain communication problem the velocity problem will solve itself without JIRA style bureaucracy.