mlsanityData to 7 Oct 2026

Predicting Issue Types on GitHub

arXiv 2107.09936 ↗First posted 21 Jul 2021cs.SE cs.LGcited by 10

Not on the map. Why?

Abstract (arXiv)

Software maintenance and evolution involves critical activities for the success of software projects. To support such activities and keep code up-to-date and error-free, software communities make use of issue trackers, i.e., tools for signaling, handling, and addressing the issues occurring in software systems. However, in popular projects, tens or hundreds of issue reports are daily submitted. In this context, identifying the type of each submitted report (e.g., bug report, feature request, etc.) would facilitate the management and the prioritization of the issues to address. To support issue handling activities, in this paper, we propose Ticket Tagger, a GitHub app analyzing the issue title and description through machine learning techniques to automatically recognize the types of reports submitted on GitHub and assign labels to each issue accordingly. We empirically evaluated the tool's prediction performance on about 30,000 GitHub issues. Our results show that the Ticket Tagger can identify the correct labels to assign to GitHub issues with reasonably high effectiveness. Considering these results and the fact that the tool is designed to be easily integrated in the GitHub issue management process, Ticket Tagger consists in a useful solution for developers.

Key facts. Cited by 10 papers in the map (data through 7 Oct 2026). Builds on 2 of its 20 references that are in the map. First posted on arXiv 21 Jul 2021.

Builds on

2 of 20 references.

References · 2

  1. 2016Bag of Tricks for Efficient Text Classificationcited by 869
  2. 2020On the feasibility of automated prediction of bug and non-bug issuescited by 6

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2022: 3; 2023: 1; 2024: 2; 2025: 3; 2026: 1.

10 papers.