[cauterized]

Jira with a kanban board for individual to-dos (we have a LOT of bugs and small change requests to track). Trello to track the big picture project pipeline.

Nothing beats Jira as a bug database in my experience because it really is a database.

But you have to configure it for your own process (which for a healthy team mostly means lifting restrictions, IME), and there's a huge learning curve for initial configuration.

Plus it can be overwhelming for non-technical people to learn to use.

My experience is that engineers grumble for a week or two about the learning curve, but if you give them generous permissions plus a walk-through a couple days in, they quickly learn to appreciate its power.