That said, our use case is explicitly tracking backlog — work that needs to get done. My philosophy is that any issue tracker that is treated as a database and that disassociates items from assignments will decay into a pile of rot almost immediately. Especially bugs. Don't put anything into the database that does not represent work to be done within the next few days.
So we use Asana as a collaboration tool that brings together stakeholders, information and assets. Typical workflow: Account manager brings issue to attention of project manager, who brings it to attention of developer, who does the work, sends it back so customer can be notified. Task goes away. Another typical workflow is an actual project, with steps to complete and a launch timeline.
The only way, in my experience, to manage bugs is to give them to a project manager. The PM triages: Forget or hide the unimportant ones away in a drawer, and fix the important ones ASAP. Bugs that linger aren't important enough to consider. Sometimes everyone is too busy and the bugs are important but not critical; schedule a single day of the week when everyone puts aside their main work and plow through the bug backlog. We call them "bug days".
For new features, use something else, like Google Docs. But it will rot, too. It's better to do whiteboard sessions that are turn into discrete tasks and discrete projects.
I haven't used it. What's the biggest feature of Asana, and how is it flawed?
So Asana is a todo list. Everything is a task. Tasks are assigned. Tasks can have subtasks. They can also have comments, tags and attachments. The top-level organizing construct is the project; projects have tasks and also team members. Oh, and within a project, tasks have order (something which doesn't really work in practice).
So far so good. Most of the problem with Asana is in the UI. Asana is all about lists. Unlike Trello, for example, Asana only has one view: A vertical list of tasks. This list UI is very much like a classic outliner or even text editor, in that there's almost always a cursor that's editing something. You can use the keyboard to navigate around. This leads to some immediate weaknesses: Since there's usually a cursor, typing something will typically have the text land in some random, unpredictable place. Hitting Enter creates an empty task. So if you're not super careful, your lists will be littered with errand characters and empty tasks.
This information-dense view means there is never a place to "rest". I can't keep a single task open. There's a split screen that allows you to maximize a task, but it's not quite the same. So in Asana, you never feel like you're in a specific location. It's always the list. It's easy to get lost because there's little or no sense of hiearchy, even though the data model is hiearchical. This UI is doubly problematic because Asana is a heavy single-page app (it takes several seconds for it to "boot") that doesn't lend itself to being opened up in multiple tabs. So it's not very web-app-like.
Really, this kind of editor-like "live" UI seems more appropriate for personal todo lists, but not for collaborative ones. In my mind, a task is a kind of mini project, and a task with subtasks is a bigger kind of mini project (usually you use these for multi-step tasks like launches or big features), but Asana treats them all with equal lightweightness. In fact, in your "My Tasks" view (also a list), Asana will comingle subtasks and top-level tasks, making it confusing because subtasks don't carry their context with them — so "My Tasks" will list something like "Add CNAME", which on its own makes no sense, until you click on it and see that it's a subtask of "superproduct.com launch".
There are lots of minor flaws. The editor is horrible — pasting and undo/redo tend to make the cursor lose its place, there's basically no support for pasting code (no syntax highlighting), the keyboard shortcuts are non-standard and weird (they use tab (!) instead of alt or ctrl as a modifier), and you can't turn off the stupid rich text mode (no Markdown). As mentioned, startup time is bad, and the main page loads as a POST, so if you restart the browser, the browser needs to ask if you "want to submit this form", which is bizarre.
The more I talk about, the less I like it. Unfortunately, so far I haven't found any alternatives that look good enough to migrate.