One of the challenges directly affecting developer's productivity in the process of fixing bug reports is the time required to search and evaluate high volumes of reported bugs. Large software systems are plagued by thousands of bug reports daily [1]}. As this number keeps increasing, the time needed to investigate these bug reports by developers becomes almost an unattainable task to achieve [2]}. Additionally, some of the bug reports are more complex than others. They contain discussion threads that are lengthy and frequently become difficult to understand as different stakeholders engage in extensive discussions [3]}. Lengthy discussions pose substantial challenge to developers who must reason about which comments in a discussion thread are relevant to finding a potential solution for the bug report that they are investigating.
