Speaking of patches, I wonder if it would be possible to introduce a 'ticket' system to the website, to make bug reporting a bit more efficient. I don't know what would be required in terms of programming, but it's just an idea anyway.
Here's an example of what I mean: https://trac.mpc-hc.org/ticket/2747
well as steven said:
i wont agree to a ticketing system as then it becomes a job and not a hobby project
Despite that, i did look at trac, bugzilla, and some other bug tracking system. AND i don't like them. they are overly complicated, UGLY!, and i highly doubt most of them will play nice with SMF forum integration(either you need to create another account OR some code tweaking).
BUT i do like github issue tracking system. It is dead simple, beautiful and conversation is forum like structured. BUT it is not open sourced

As Steven pointed out managing ticket require some effort, and the current MusicBee site redesign is mainly to reduce effort for both Steven and Addon devs while also reducing effort of new users.
Here is what i think would work:
1. Dead Simple github style issue browsing
2. elegant and easy to use.
3. Forum login integration.
4. Support for issue status such as
opened
closed
planned
done
5. conversation between users and others.
The main problem is with each opened issue you have to close it(or done) when the issue is fixed. AND THAT IS ONE BIG PROBLEM! you have to keep track or browse through EVERY issue and mark it.
as now if user create a topic on the forum Steven replies to it and if the issue solved it is well else it either get planned for next release or planned for future or addon. BUT steven don't have to reply back WHEN that particular issue is fixed a week/month later. also you don't have to do CLOSE or PLANNED status.