• Corpus ID: 231942416

Improved dependency management for issue trackers in large collaborative projects

  title={Improved dependency management for issue trackers in large collaborative projects},
  author={Mikko Raatikainen and Quim Motger and Clara Marie L{\"u}ders and Xavier Franch and Lalli Myllyaho and Elina Kettunen and Jordi Marco and Juha Tiihonen and Mikko Halonen and Tomi M{\"a}nnist{\"o}},
Issue trackers, such as Jira, have become the prevalent collaborative tools in software engineering for managing issues, such as requirements, development tasks, and software bugs. However, issue trackers inherently focus on the life-cycle of single issues although issues have and express dependencies on other issues that constitute an issue dependency network in a large complex collaborative projects. The objective of this study is to develop supportive solutions for the improved management of… 

Figures and Tables from this paper

Mining Dependencies in Large-Scale Agile Software Development Projects: A Quantitative Industry Study
It is concluded that leveraging ALM monitoring data to automatically detect dependencies could help Agile teams address work coordination needs and manage risks related to dependencies in a timely manner.


OpenReq Issue Link Map: A Tool to Visualize Issue Links in Jira
This work presents a Jira plug-in that supports developers, project managers, and product owners in managing and overviewing issues and their dependencies, and helps to find missing or unknown links between issues, and detects inconsistencies.
No issue left behind: reducing information overload in issue tracking
A developer-centric approach to issue tracking that aims to reduce information overload and improve developers' situational awareness is presented and can reduce the volume of irrelevant emails by over 99% and also improve support for specific issue-tracking tasks.
Communication, collaboration, and bugs: the social nature of issue tracking in small, collocated teams
A qualitative study of issue tracking systems as used by small, collocated software development teams found that an issue tracker is not just a database for tracking bugs, features, and inquiries, but also a focal point for communication and coordination for many stakeholders within and beyond the software team.
Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub
This study investigates and answers various research questions on the popularity and impact of issue trackers, and performs an empirical study on a hundred thousands of open source projects.
An analysis of requirements evolution in open source projects: recommendations for issue trackers
Investigation of six open source projects and their users led to a number of important observations and a categorization of the root causes of these duplicates, and a set of improvements for future issue tracking systems are proposed.
Issue Tracking System with Duplicate Issue Detection
Quality Assurance System (QAS) tries to find out facilities which are absent in existing systems and adding feature as duplicate issue detection effectively and calculate developers performance to improve their performance to get appraisal.
RESim - Automated Detection of Duplicated Requirements in Software Engineering Projects
RESim is a software development proposal which integrates different techniques for the detection of duplicated requirements in an adaptive, scalable tool to deliver an easy-to-use, practical tool for duplication requirements detection for requirements engineers and to provide an evaluation framework of different similarity detection algorithms for researchers.
A contextual approach towards more accurate duplicate bug report detection
It is concluded that researchers should not ignore the context of software engineering when using IR tools for deduplication, and contextual information, relying on prior knowledge of software quality, software architecture, and system-development topics, can be exploited to improve bug-deduplications.
Bug Report Networks: Varieties, Strategies, and Impacts in a F/OSS Development Community
Findings are presented from an investigation of the nature, extent, and impact of BRNs in one large F/OSS development community that investigates whether and how specific classes ofBRNs influence problem management within the community, and identifies several new research questions.
Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability
A systematic mapping of IR-based trace recovery is conducted, with a particular focus on previous evaluations and strength of evidence, and it is concluded that the overall quality of reporting should be improved regarding both context and tool details, measures reported, and use of IR terminology.