I'm actually a CTO and product manager. We use Asana for high level planning and github issues for tracking detailed technical work. We design using Figma. Our developers don't go near Asana generally. We have our roadmap and backlog in Asana though and we track some non technical topics there for e.g. management, hr, sales, support, etc. It's good for high level stuff and usable by non technical people.
And since I'm in charge, this is an Atlassian free company and that's not an accident. I can work with their stuff but I prefer using the tools I mentioned over their stuff.
The reason I like github issues for product management is that they are easy to connect to pull requests and you can close them by mentioning them in commit messages. This cuts down on process bureaucracy, which means less work for me. IMHO any issue tracker needs similar deep integration with the development process like that. End to end life cycle tracking from inception to deployment for any feature and enhancement is key.
I also love using meta tracking tickets where I can easily convert TODO items into new tickets, refer existing tickets and PRs, etc. From a project and product management point of view that's great. Labels, milestones, etc. make this easier. And of course being able to use Markdown everywhere is nice too.
It's not perfect unfortunately and I'd love a unified ui with tickets from all our github repositories. Their project tool is a weird one; on paper it could do that. But it seems unable to do any sensible integration with the issue tracker unless you configure a lot of actions to copy things over which seems madness to me.