"Silent Is Not Actually Silent": An Investigation of Toxicity on Bug Report Discussion

Fuente: arXiv
Salvato in:
Dettagli Bibliografici
Autori principali: Imran, Mia Mohammad, Sarker, Jaydeb
Natura: Preprint
Pubblicazione: 2025
Soggetti:
Accesso online:
Tags: Aggiungi Tag
Nessun Tag, puoi essere il primo ad aggiungerne!!
_version_ 1866909598568415232
author Imran, Mia Mohammad
Sarker, Jaydeb
author_facet Imran, Mia Mohammad
Sarker, Jaydeb
contents 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.
format Preprint
id arxiv_https___arxiv_org_abs_2503_10072
institution arXiv
publishDate 2025
record_format arxiv
spellingShingle "Silent Is Not Actually Silent": An Investigation of Toxicity on Bug Report Discussion
Imran, Mia Mohammad
Sarker, Jaydeb
Software Engineering
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.
title "Silent Is Not Actually Silent": An Investigation of Toxicity on Bug Report Discussion
topic Software Engineering
url https://arxiv.org/abs/2503.10072