I think it is a big disservice for this module to be presented as a Bug Tracker even though that is its origin. I think it should be positioned as a general-purpose tracking/task module. I believe it has a lot more application potential as non-BugTracker. I, for one, want to use it as a HelpDesk for students, that is a ticketing system, in one Moodle and for submitting changes for a normal web site in another Moodle which functions as Intranet, so the web team can handle them accordingly. I can envision it being used by student teams for tasking projects. Moodle support stuff can use it to track internal maintenance tasks. Ans so on. Some people may use it for real bug tracking but I suspect it will be a minority.

The module could retain the name Tracker (not BugTracker as it says in some places) and have the language file reworked to drop all references to bugs and replace them with, for example, issues. That is all what needs to be done. The only problem with the name "tracker" is that it will likely be regularly confused with the issue tracker at moodle.org (the filter in forums, for example, automatically links word "tracker" to that site). I thought of Ticket Module, Issue Module, Task Module, and several variations thereof as posibilities to consider.