So, the situation is this - my company manages a big (~400 people) closed beta project. We want to implement some kind of issue tracking system that will enable us and the testers to better manage our issues. Right now we encounter tons of duplicate issues, issues that are important but being buried somewhere in the forums, and a lot of knowledge is lost in the process.
What kind of solution is available to improve the current situation but without exposing the entire development process to the beta community?
I would also like to hear about any experience with exposing issue tracking to a community.