Abstract: Technologies for reliably and efficiently mapping any particular bug report identifying a target component to a relevant owner who is currently responsible for handling the bug report. This mapping involves considering a list of developers that have historically and currently contributed to the identified target component, ranking each contributing developer based on a measure of recency of his contribution, considering a list of the managers of the contributing developers, ranking each manager based on the rankings of his contributing developers, identifying an area path (“AP”) in an AP hierarchy based on these rankings, mapping the identified AP to a current AP, determining, based on the current AP, a relevant owner of the identified target component, and assigning the bug report to the relevant owner.