| this is not what i thought it was the term "triage" means to order items (patients, originally) according to urgency this paper has nothing whatever to do with sorting a bug list according to urgency the paper describes a model to assign a particular bug to the developer who can resolve it most efficiently to me this is "assignment" not "triaging" but at least you can see how a supervised learning technique is a good fit for the problem they actually describe so one row in the training set is a set of attributes relating to the bug itself--where in the codebase it resides, etc the class labels are of course the developers assigned to fix the bug what actually is presented in this paper might be useful--although i have my doubts that the net value of such a model (optimum assignment of devs to bugs). In other words, even if the model can generate assignments better and more efficiently than manual assignment, the developer time required to write the code to convert the raw data to model input (to train/test/validate the model) is not small--for intance, look at how much unstructured text is involved i doubt i would go to the trouble--mapping devs to bugs is nothing something we do poorly at my shop, and even when i get it wrong, the devs sort it out by swaping out tickets not nearly as useful as an automated bug triaging sytem--ie, a system that would auto-sort our bug list based on urgency, but again, that's not the subject of this paper, title notwithstanding. |