The issue report classification competition consists of building and testing a set of multi-class classification models to classify issue reports as belonging to one category representing the type of information they convey.
We provide a dataset encompassing 3 thousand labeled issue reports (as bugs, enhancements, and questions) extracted from 5 real open-source projects. You are invited to leverage this dataset for evaluating your classification approaches and compare the achieved results against proposed baseline approaches based on Sentence-Transformers.
You must train, tune and evaluate your multi-class classification models using the provided training and test sets.
Please refer to our tool competition page to read more about the tool competition and learn how to participate.
Since you will be using our dataset (and possibly one of our notebooks) as well as the original work behind the dataset, please cite the following references in your paper:
@inproceedings{nlbse2024,
author={Kallis, Rafael and Colavito, Giuseppe and Al-Kaswan, Ali and Pascarella, Luca and Chaparro, Oscar and Rani, Pooja},
title={The NLBSE'24 Tool Competition},
booktitle={Proceedings of The 3rd International Workshop on Natural Language-based Software Engineering (NLBSE'24)},
year={2024}
}@article{kallis2020tickettagger,
author={Kallis, Rafael and Di Sorbo, Andrea and Canfora, Gerardo and Panichella, Sebastiano},
title={Predicting issue types on GitHub},
journal={Science of Computer Programming},
volume={205},
pages={102598},
year={2021},
issn={0167-6423},
doi={https://doi.org/10.1016/j.scico.2020.102598},
url={https://www.sciencedirect.com/science/article/pii/S0167642320302069}
}@inproceedings{kallis2019tickettagger,
author = {Kallis, Rafael and Di Sorbo, Andrea and Canfora, Gerardo and Panichella, Sebastiano},
title = {Ticket Tagger: Machine Learning Driven Issue Classification},
booktitle = {2019 {IEEE} International Conference on Software Maintenance and Evolution,
{ICSME} 2019, Cleveland, OH, USA, September 29 - October 4, 2019},
pages = {406--409},
publisher = { {IEEE} },
year = {2019},
doi = {10.1109/ICSME.2019.00070},
}@inproceedings{colavito2023few,
author={Colavito, Giuseppe and Lanubile, Filippo and Novielli, Nicole},
booktitle={2023 IEEE/ACM 2nd International Workshop on Natural Language-Based Software Engineering (NLBSE)},
title={Few-Shot Learning for Issue Report Classification},
year={2023},
volume={},
number={},
pages={16-19},
doi={10.1109/NLBSE59153.2023.00011}
}A dataset of 3 thousand publicly-available issue reports is extracted.
Each issue report contains the following information:
- Repository
- Label
- Title
- Body
Each issue is labeled with one class that indicates the issue type, namely, bug, feature, and question.
Issues with multiple labels are excluded from the dataset.
The dataset is then split into a training set (50%) and a test set (50%).
The process of extracting the dataset is described in the dataset notebook.
The dataset has already been extracted to avoid costs on your end, please keep reading to find hyperlinks to both the training and test set.
You are provided a training set encompassing 1.5 thousand labeled issue reports extracted from 5 real open source projects. The training-set is balanced, i.e., it contains the same number of issues for each class.
Participants must train a multi-class classifier for each of the 5 projects, i.e., we expect 5 classifiers per model submission.
Participants are free to select and transform variables from the training set as they please. Pretrained models are permitted but can only be finetuned on the given training set. Any inputs or features used to create or finetune the classifier, must be derived from the provided training set. Participants may preprocess, sample, apply over/under-sampling, select a subset of the attributes, perform feature-engineering, filter records, split the training set into a model-finetuning validation set, etc. Please contact us if you have any question about this.
Submissions are evaluated based on their class-detection performance over the provided test set. The classifier should assign one label to an issue. Just like the training set, the test set is balanced.
Participants must evaluate their project classifiers on the test set of the respective project and report the results in their submission.
Important: you may apply any preprocessing or feature engineering on this dataset except sampling, rebalancing, undersampling or oversampling techniques.
Repository classification performance is measured using the F1 score over all the three classes (averaged). Cross-repository performance is measured as the arithmetic mean of the five repository F1 scores.
A submission (i.e., paper) in the tool competition must provide, for each of the 5 repositories and cross-repo:
- Precision, for each class and cross-class average
- Recall, for each class and cross-class average
- F1 score, for each class and cross-class average
Cross-class aggregation can be done using both the macro and micro averaging method, the result will be the same since the dataset is balanced.
Cross-repo aggregation is done using the arithmetic mean.
Please note that whilst all of the above measures must be provided for acceptance, the submissions will only be ranked by their cross-repo F1 score.
You can use the table from the baseline below as a template for your evaluation.
Participants are encouraged, but not required, to use the baseline as a template for their submission. Each template downloads the dataset, performs basic preprocessing, trains a set of classifiers and evaluates them on the test set.
| Repository | Label | Precision | Recall | F1 |
|---|---|---|---|---|
| facebook/react | bug | 0.9048 | 0.9500 | 0.9268 |
| facebook/react | feature | 0.8491 | 0.9000 | 0.8738 |
| facebook/react | question | 0.8652 | 0.7700 | 0.8148 |
| facebook/react | average | 0.8729 | 0.8733 | 0.8718 |
| tensorflow/tensorflow | bug | 0.9565 | 0.8800 | 0.9167 |
| tensorflow/tensorflow | feature | 0.8558 | 0.8900 | 0.8725 |
| tensorflow/tensorflow | question | 0.7885 | 0.8200 | 0.8039 |
| tensorflow/tensorflow | average | 0.8669 | 0.8633 | 0.8644 |
| microsoft/vscode | bug | 0.8485 | 0.8400 | 0.8442 |
| microsoft/vscode | feature | 0.7627 | 0.9000 | 0.8257 |
| microsoft/vscode | question | 0.8916 | 0.7400 | 0.8087 |
| microsoft/vscode | average | 0.8343 | 0.8267 | 0.8262 |
| bitcoin/bitcoin | bug | 0.7604 | 0.7300 | 0.7449 |
| bitcoin/bitcoin | feature | 0.8723 | 0.8200 | 0.8454 |
| bitcoin/bitcoin | question | 0.6455 | 0.7100 | 0.6762 |
| bitcoin/bitcoin | average | 0.7594 | 0.7533 | 0.7555 |
| opencv/opencv | bug | 0.7619 | 0.8000 | 0.7805 |
| opencv/opencv | feature | 0.8842 | 0.8400 | 0.8615 |
| opencv/opencv | question | 0.8100 | 0.8100 | 0.8100 |
| opencv/opencv | average | 0.8187 | 0.8167 | 0.8173 |
| overall | bug | 0.8464 | 0.8400 | 0.8426 |
| overall | feature | 0.8448 | 0.8700 | 0.8558 |
| overall | question | 0.8001 | 0.7700 | 0.7827 |
| overall | average | 0.8305 | 0.8267 | 0.8270 |