"Silent Is Not Actually Silent": An Investigation of Toxicity on Bug
  Report Discussion
Toxicity in bug report discussions poses significant challenges to the
collaborative dynamics of open-source software development. Bug reports are
crucial for identifying and resolving defects, yet their inherently
problem-focused nature and emotionally charged context make them susceptible to
toxic interactions. This study explores toxicity in GitHub bug reports through
a qualitative analysis of 203 bug threads, including 81 toxic ones. Our
findings reveal that toxicity frequently arises from misaligned perceptions of
bug severity and priority, unresolved frustrations with tools, and lapses in
professional communication. These toxic interactions not only derail productive
discussions but also reduce the likelihood of actionable outcomes, such as
linking issues with pull requests. Our preliminary findings offer actionable
recommendations to improve bug resolution by mitigating toxicity.
67d390de29a092bdbb0a2aeb
Mia Mohammad Imran
extracted_confirmed
2025-03-14T02:14:33.331Z
6331c3f618711776b468e9ec
/avatars/af2c4bba031e474bf4fd2ea19e415aaf.svg
Mia Mohammad Imran
user
imranraad
67d390de29a092bdbb0a2aec
Jaydeb Sarker
"Silent Is Not Actually Silent": An Investigation of Toxicity on Bug
  Report Discussion
Toxicity in bug report discussions poses significant challenges to the
collaborative dynamics of open-source software development. Bug reports are
crucial for identifying and resolving defects, yet their inherently
problem-focused nature and emotionally charged context make them susceptible to
toxic interactions. This study explores toxicity in GitHub bug reports through
a qualitative analysis of 203 bug threads, including 81 toxic ones. Our
findings reveal that toxicity frequently arises from misaligned perceptions of
bug severity and priority, unresolved frustrations with tools, and lapses in
professional communication. These toxic interactions not only derail productive
discussions but also reduce the likelihood of actionable outcomes, such as
linking issues with pull requests. Our preliminary findings offer actionable
recommendations to improve bug resolution by mitigating toxicity.
Toxicity in GitHub bug reports arises from misaligned perceptions of severity and priority, unresolved frustrations with tools, and lapses in professional communication, hindering productive discussions and actionable outcomes.