OpenReq Issue Link Map: A Tool to Visualize Issue Links in Jira

Lüders, Clara Marie; Raatikainen, Mikko; Motger, Joaquim; Maalej, Walid

doi:10.1109/re.2019.00070

Cited by 5 publications

(8 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the users' side, Issue Link Map [34] (Figure 3) is embedded in the Jira plugin (Fisutankki), which creates a browser-based user interface (→usability, compatibility). A central part of the user interface is a 2D representation of a p-depth issue graph (G p 0 ).…”

Section: Artifact Designmentioning

confidence: 99%

Improved Management of Issue Dependencies in Issue Trackers of Large Collaborative Projects

Raatikainen

Motger

Lüders

et al. 2023

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

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 lifecycle of single issues, although issues have and express dependencies on other issues that constitute issue dependency networks in large complex collaborative projects. The objective of this study is to develop supportive solutions for the improved management of dependent issues in an issue tracker. This study follows the Design Science methodology, consisting of eliciting drawbacks and constructing and evaluating a solution and system. The study was carried out in the context of The Qt Company's Jira, which exemplifies an actively used, almost two-decade-old issue tracker with over 100,000 issues. The drawbacks capture how users operate with issue trackers to handle issue information in large, collaborative, and long-lived projects. The basis of the solution is to keep issues and dependencies as separate objects and automatically construct an issue graph. Dependency detections complement the issue graph by proposing missing dependencies, while consistency checks and diagnoses identify conflicting issue priorities and release assignments. Jira's plugin and service-based system architecture realize the functional and quality concerns of the system implementation. We show how to adopt the intelligent supporting techniques of an issue tracker in a complex use context and a large data-set. The solution considers an integrated and holistic system view, practical applicability and utility, and the practical characteristics of issue data, such as inherent incompleteness.

show abstract

Section: Artifact Designmentioning

confidence: 99%

Improved Management of Issue Dependencies in Issue Trackers of Large Collaborative Projects

Raatikainen

Motger

Lüders

et al. 2023

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Regarding the specific information for maintaining trace links, Luders et al noted that it is difficult to maintain an overview of dependencies among issues [32]. Çetin et al focused on identifying the contributions of developers based on traceability graphs [55].…”

Section: ) Informationmentioning

confidence: 99%

“…Three studies focused on the trace links among issue reports [32], [40], [43], [49]. The studies in [40], [43] focused on the different kinds of trace links, such as related links, duplicates, and blocks.…”

Section: ) Issue Reportsmentioning

confidence: 99%

A Systematic Literature Review of Issue-Based Requirement Traceability

et al. 2023

View full text Add to dashboard Cite

Issue reports are software artifacts that often specify the changed requirements of software systems. As software systems evolve according to these changed requirements, issue reports have become the essential artifacts that should be covered by requirement traceability. While researchers have developed automatic approaches for establishing the traceability links of issue reports, no papers have surveyed these approaches. In this paper, we conduct a systematic literature review of issue-based requirement traceability. We searched for articles published in renowned conferences and journals in the software engineering field from 2011 to 2022. From 1,347 initial articles, we identified 40 relevant articles. We investigated four aspects of issue-based traceability: problems, artifact pairs, techniques, and evaluation targets. Our findings are as follows. First, the challenges of issue-based requirement traceability are relevant to accuracy, effort, support, information, and trustworthiness. Second, issue reports are linked to commits, source code, user reviews, and test cases. Third, the studies mainly adopted machine learning and information retrieval techniques to generate and recover trace links. Finally, the main evaluation targets were open-source projects, but open datasets were also provided.

show abstract

“…On the users' side, Issue Link Map [28] (Figure 3) is embedded in the Jira plug-in (Fisutankki), which creates a browser-based user interface (→usability, compatibility). A central part of the user interface is a 2D representation of a p-depth issue graph (G p 0 ).…”

Section: Artifact Designmentioning

confidence: 99%

Improved dependency management for issue trackers in large collaborative projects

Raatikainen,

Motger,

Lüders

et al. 2021

Preprint

Self Cite

View full text Add to dashboard Cite

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 dependent issues in an issue tracker. This study follows Design Science methodology, consisting of elicitation of drawbacks, and construction and evaluation of a solution and system. The study was carried out in the context of The Qt Company's Jira, which exemplifies an actively used, almost two decade old issue tracker with over 100,000 issues. The drawbacks capture how users operate with issue trackers to handle issue information in large, collaborative and long-lived projects. The basis of the solution is to keep issues and dependencies as separate objects and automatically construct an issue graph. Dependency detection complements the issue graph by proposing missing dependencies, and consistency check and diagnosis identify incompatible issue priorities and release assignments. Jira's plugin and service-based system architecture realizes the functional and quality concerns of the system implementation. We show how to adopt the supporting intelligent techniques of an issue tracker in a complex use context and a large data-set. The solution takes into account integrated and holistic system-view, practical applicability and utility, and the practical characteristics, such as inherent incompleteness, of issue data.

show abstract

OpenReq Issue Link Map: A Tool to Visualize Issue Links in Jira

Cited by 5 publications

References 4 publications

Improved Management of Issue Dependencies in Issue Trackers of Large Collaborative Projects

Improved Management of Issue Dependencies in Issue Trackers of Large Collaborative Projects

A Systematic Literature Review of Issue-Based Requirement Traceability

Improved dependency management for issue trackers in large collaborative projects

Contact Info

Product

Resources

About