Personally i use a combination of Uservoice and Github (if open) or otherwise find a way to make the internal bug tracker readable to the public.
Personally i use a combination of Uservoice and Github (if open) or otherwise find a way to make the internal bug tracker readable to the public.
One thing to consider here is the difference between "help us track our bugs" and "let's build a community around our product". In the long run, the community will be far more valuable than merely acknowledging a feature request or bug report.
There are a lot of bugs and even feature requests that require a fair bit of back and forth discussion, both internal and external, to decide what the best approach is. I like GitHub for straightforward bugs, but it is not great for discussion. And involving your active users / customers in the future of your product, including your own team, is a huge strategic advantage.