Issue Tracking Ecosystems: Context and Best Practices
Lloyd Montgomery

TL;DR
This paper explores Issue Tracking Ecosystems (ITEs), analyzing their complexity and diversity through practitioner interviews and archival data, and proposes a Best Practice Ontology to improve understanding and management.
Contribution
It introduces a comprehensive analysis of ITEs' context-dependent challenges and presents a structured ontology to align research and practice in issue tracking.
Findings
ITE problems are highly context-dependent.
Existing solutions lack consistent framing and comparability.
The proposed ontology aims to standardize best practices.
Abstract
Issue Tracking Systems (ITSs), such as GitHub and Jira, are popular tools that support Software Engineering (SE) organisations through the management of ``issues'', which represent different SE artefacts such as requirements, development tasks, and maintenance items. ITSs also support internal linking between issues, and external linking to other tools and information sources. This provides SE organisations key forms of documentation, including forwards and backwards traceability (e.g., Feature Requests linked to sprint releases and code commits linked to Bug Reports). An Issue Tracking Ecosystem (ITE) is the aggregate of the central ITS and the related SE artefacts, stakeholders, and processes -- with an emphasis on how these contextual factors interact with the ITS. The quality of ITEs is central to the success of these organisations and their software products. There are challenges,…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering Research · Software Engineering Techniques and Practices · Scientific Computing and Data Management
