I think you shouldn’t mix support facilities with bug trackers and code review tools. In most processes, problems the support department can’t solve are issued as bugs, but since support can solve many problems the bug tracker is not spammed with entries by end-users which usually lack important information (like OS version, exact steps to reproduce the problem etc.) which the support would ask for.
But speaking of community facilities: What I would really welcome would be if Fairphone developers would a public platform like GitHub (or something similar) for development. They can have another private repo, but from there they should push the changes to such a public repo, so all changes could be easily tracked over the web without installing a git client and syncing the code. A good example is cmxlog which aggregates the commit history for multiple repositories into a unified view:
And once we have that, the issue tracker could be the next step. One issue here is though that you typically have several different repositories for android development, but most people would have a hard time to determine which component is the one to issue the bug report for.
Regarding the wiki-style bug list here on the forum: Yes this is very cool and much better than what you typically see in other Android community forums, especially in forums run by the vendor itself! I would opt for keeping it this way, but to have this “developer friendly” issue tracker as well and link each issue to both the forum thread with the discussion and the issue tracker entry.