The role of surprisal in issue trackers
Context: Software development creates and relies on a large volume of information, yet the volume of this information can make it challenging for developers to maintain an overview of all goings-on that a team and external actors contribute to a project. We posit that unexpected or “surprising” even...
Saved in:
Main Authors: | , , , |
---|---|
Format: | text |
Language: | English |
Published: |
Institutional Knowledge at Singapore Management University
2025
|
Subjects: | |
Online Access: | https://ink.library.smu.edu.sg/sis_research/9845 https://ink.library.smu.edu.sg/context/sis_research/article/10845/viewcontent/Role_Surprisal_Issue_Trackers_av.pdf |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | Singapore Management University |
Language: | English |
Summary: | Context: Software development creates and relies on a large volume of information, yet the volume of this information can make it challenging for developers to maintain an overview of all goings-on that a team and external actors contribute to a project. We posit that unexpected or “surprising” events could serve as important signposts amidst this information overload. These unexpected events may indicate underlying anomalies or emergent situations that require immediate attention. To explore this premise, our study leverages the concept of ‘surprisal’ from information theory to identify and quantify these unusual occurrences from the issues and pull requests of popular open-source software repositories. Objective: Drawing from a previously published research protocol, our study investigates whether a correlation exists between the ‘surprisal’ of issues and their perceived importance or difficulty within software repositories. Results: We performed a comprehensive analysis of approximately two million issues and pull requests, gathered from 1,270 repositories. Their ‘surprisal’ was then examined in relation to several indicative metrics of difficulty and perceived importance. Our results indicate only a weak correlation. This outcome underscores the need for further research to devise more effective strategies for helping developers prioritise issues. |
---|