No. We users, don’t create bugs, so, there aren’t our bugs. We can find them and report. Some bugs I could report just don’t affect me, but affects other people, and, as a bug, affects Xojo as a product. In the role of bug reporter probably I’ll not babysitting bug fixes ( good for the sanity of Xojo engineers ). It’s more like a “report and forget” unless additional data are requested. I must believe that the professionals will take care of it, not push them to the limbo bin and after 2 years guilt us of not taking caring of them. In other systems, this way of interpreting bug reporting/fixing is simply impossible.
You are absolutely RIGHT!
You, as a high level engineer, shouldn’t be doing this! You shouldn’t be on the front line unless necessary. You should be in the second line. SOMEONE, trained as a tester, should be doing the FIRST review, closing improper reports, requesting more data, and when the case is solid then assign the case for the proper people. You will always have solid reports and feature requests unless the reviewers have doubts and send the case right to you for your judgment/analysis . This part of the job of first analysis, filtering, adding comments and data, and sending the case to the proper teams/resources/engineers, should be the task of other people, while you are concentrated in fixing, development, and emptying your task queue as your other colleagues. Some manager at Xojo would check how bad the fixing work is, how the piles of work per engineer are evolving and request more people when some engineers are getting overloaded, etc.
That said, I know Xojo is not Microsoft. Task management, as I told, not losing reports, fixes and feature requests, is simple. It’s tested and works, BUT probably needs more money to be implemented than the current model, because I feel Xojo would need more people. And as I told, when the technical part touches the business part, I can’t comment anymore.
My point of view was already exposed, I don’t intend to extend this topic.