Situational Awareness: Personalizing Issue Tracking Systems (original) (raw)
Related papers
Issue Tracking Systems: What Developers Want and Use
Proceedings of the 13th International Conference on Software Technologies
An Issue Tracking System (ITS) allows a developer to keep track of, prioritize, and assign multitudes of bugs, feature requests, and other development tasks such as testing. Despite ITSs play a significant role in day-today developers' activities, no previous study investigated what developers want and use in an ITS. The aim of this paper is twofold. First, we provide a feature matrix that maps six of the most used ITS to features, and second, we measure the developers' level of use and perceived importance of each feature. This knowledge has multiple benefits such as supporting the decision of the ITS to use and revealing promising areas of research and development. Specifically, quality improvement effort should target improving functionality in use, and development effort should target supporting functionalities needed. In this paper, we define and extract ten core ITS features and asked more than a hundred developers to rate their importance and use. Our results show that Advanced Search and Flexible Notifications are the most important features. Moreover, results show that no feature has been used by more than 90% of the respondents. Another interesting finding is that 27% of respondents rate Workflow Automation as a useful or required feature, despite having never used it themselves; this suggests the need to better training, exposure or of availability of ITS features. In conclusion, our results pave the way to significant research and development effort on ITS.
MAITH: a meta-software agent for issue tracking help
Issue tracking is an essential part of regulated software development where it is typically supported by software systems which are complex and not easily customizable. We propose a meta-software agent that senses what windows and widgets are in focus by the user and leverages this awareness to provide support. The user is given ways of making and recalling annotations appropriate for the context. By observing users in action the agent creates models which can then be used to predict and suggest next steps. This paper describes an early prototype of this approach built as a proof of concept. Preliminary results and directions for future work are outlined.
Communication, collaboration, and bugs: The social nature of issue tracking in software engineering
2010
ABSTRACT Issue tracking systems help organizations manage issue reporting, assignment, tracking, resolution, and archiving. Traditionally, it is the Software Engineering community that researches issue tracking systems, where software defects are reported and tracked as 'bug reports' within an archival database. Yet issue tracking is fundamentally a social process and, as such, it is important to understand the design and use of issue tracking systems from that perspective.
Web-based issue tracking for large software projects
IEEE Internet Computing, 1998
Many problems are found and fixed during the development of a software system. The Project Issue Tracking System toolkit, a Web-based issuemanagement tool, can be used to organize issue reports during development and to communicate with different project teams around the world.
On the Use of Issue Tracking Annotations for Improving Developer Activity Metrics
Advances in Software Engineering, 2011
Understanding and measuring how teams of developers collaborate on software projects can provide valuable insight into the software development process. Currently, researchers and practitioners measure developer collaboration with social networks constructed from version control logs. Version control change logs, however, do not tell the whole story. The collaborative problem-solving process is also documented in the issue tracking systems that record solutions to failures, feature requests, or other development tasks. We propose two ...
Improved dependency management for issue trackers in large collaborative projects
ArXiv, 2021
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...
Bug Tracking, Help Desk Ticketing, issue raising, search facility, help information, issue resolution. Issues related to software projects can be raised, tracked and resolved by Employees of different departments. Resolved issues can be allowed to access from Knowledge Base as Knowledge elements. The different groups and representatives can interact each other through emails. The issue tracking system does all the jobs that are done in conventional system but ,here , everything is done in more formal and efficient manner. All the users of organization can interact with each other through the Issue Tracking System. This system acts as an interface between the employees thereby enabling them to forward their issues to the centralized Issue tracking system. Hence, making the work easy for both the issue raiser and the resolved. It totally avoids the involvement of middlemen in getting resolution for a particular issue.The Issue Tracking system is an intranet application, which provides information about issues in software projects, in detail. This product develops a system that can be used by all the departments of a software organization. In the conventional method, all the issues are dealt manually .The progress of the issues are also checked in person, which is a tedious task. Here, in Issue Tracking, it fulfills different requirements of administrator and employees of a software development organization efficiently. The specific purpose of the system is to gather and resolve issues that arise in different projects handled by the organization
2010
ABSTRACT Issue tracking systems help organizations manage issue reporting, assignment, tracking, resolution, and archiving. Traditionally, it is the Software Engineering community that researches issue tracking systems, where software defects are reported and tracked as 'bug reports' within an archival database. Yet, as issue tracking is fundamentally a social process, it is important to understand the design and use of issue tracking systems from that perspective.
Advisor agent support for issue tracking in medical device development.
AAAI Innovative Applications of AI (IAAI), 2012
This case study concerns the use of software agent advisors to improve efficiency and quality in issue tracking activities of development teams at the world's largest medical device manufacturer. Each software agent monitors, interacts with, and learns from its environment and user, recognizing when and how to provide different kinds of advice and support to facilitate issue tracking activities without directly modifying anything or otherwise violating domain constraints. The deployed software agent has not only enjoyed regular and growing use, but contributed to significant improvements. Issue rejection was significantly reduced and more focused, yielding significant quality and efficiency gains such as fewer reviews by quality assurance. This success reflects the benefits of the underlying AI technology.
Improved Management of Issue Dependencies in Issue Trackers of Large Collaborative Projects
IEEE Transactions on Software Engineering
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.