# An Alternative Issue Tracking Dataset of Public Jira Repositories

arXiv: https://arxiv.org/abs/2201.08368 · HTML: https://mlsanity.com/paper/2201.08368/

## Key facts

- Cited by 3 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 20 Jan 2022.

## Built on by (most cited first, 3 of 3)

- [Beyond Duplicates: Towards Understanding and Predicting Link Types in Issue Tracking Systems](https://mlsanity.com/paper/2204.12893/) (2022)
- [Identifying Technical Debt and Its Types Across Diverse Software Projects Issues](https://mlsanity.com/paper/2408.09128/) (2024)
- [How Well Can AI Generate Backlogs from App Mockups?](https://mlsanity.com/paper/2607.22902/) (2026)

## Abstract (arXiv)

Organisations use issue tracking systems (ITSs) to track and document their projects' work in units called issues. This style of documentation encourages evolutionary refinement, as each issue can be independently improved, commented on, linked to other issues, and progressed through the organisational workflow. Commonly studied ITSs so far include GitHub, GitLab, and Bugzilla, while Jira, one of the most popular ITS in practice with a wealth of additional information, has yet to receive similar attention. Unfortunately, diverse public Jira datasets are rare, likely due to the difficulty in finding and accessing these repositories. With this paper, we release a dataset of 16 public Jiras with 1822 projects, spanning 2.7 million issues with a combined total of 32 million changes, 9 million comments, and 1 million issue links. We believe this Jira dataset will lead to many fruitful research projects investigating issue evolution, issue linking, cross-project analysis, as well as cross-tool analysis when combined with existing well-studied ITS datasets.