Abstract
Software changes, new features and bugs are generally reported as issue requests which need to be quickly and efficiently resolved. A large amount of approaches have been proposed to recommend suitable developers to resolve software issues [1, 2, 6, 3]. These techniques tend to recommend senior developers who have luxuriant developing experience, which prejudice someone who just joined the team. But when the senior developers are not available, these approaches cannot effectively help select an alternative suitable developer (maybe a junior developer) to implement the issue. On the other hand, the junior developers may be not skilled to the issue request and target system. They may also need to refer to other software repositories in understanding the changing task, which is costly and time-consuming.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
