Communication, Collaboration, and Bugs: The Social Nature of Issue Tracking in Software Engineering

@inproceedings{Bertram2009CommunicationCA,
  title={Communication, Collaboration, and Bugs: The Social Nature of Issue Tracking in Software Engineering},
  author={Dane Bertram and Amy Voida and Saul Greenberg and Robert J. Walker},
  year={2009}
}
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. Consequently, we conducted a… 

Challenges and opportunities for software change request repositories: a systematic mapping study

TLDR
A systematic mapping study is performed to characterize the research field of change request (CR) repositories and investigates tools and services for CR management, to understand whether and how they addressed the topics identified.

How to Communicate when Submitting Patches

TLDR
An empirical study on the Linux kernel found that the "individual factors" plays a special role in communication, which may lead to potential problems even in accepted patches, and discusses the recommendations for different practitioners, including patch submitters, reviewers, and tool designers.

Examining Active Error in Software Development Conference or Workshop Item

TLDR
Findings demonstrate that the significance of active error in software development is personal, shaped by passing time, the emergence of preferred practices and environmental changes.

Customized awareness: recommending relevant external change events

TLDR
This paper presents a recommendation approach for filtering the flood of change events on deployment dependencies to those that are most likely to cause problems for the individual developer and is evaluated for its ability to drastically filter irrelevant details while being unlikely to filter important ones.

Examining active error in software development

TLDR
Findings demonstrate that the significance of active error in software development is personal, shaped by passing time, the emergence of preferred practices and environmental changes.

The Open University ’ s repository of research publications and other research outputs Examining Active Error in Software Development

TLDR
Findings demonstrate that the significance of active error in software development is personal, shaped by passing time, the emergence of preferred practices and environmental changes.

Towards prioritizing user-related issue reports of mobile applications

TLDR
This paper proposes an approach to map issue reports that are recorded in issue tracking systems to user-reviews, and uses the top apps in terms of star-ratings to train a model for prioritizing issue reports.

A Survey of Knowledge Capture and Knowledge Sharing Techniques in Agile Software Companies

TLDR
A survey has been carried out in ten agile-based software companies in Mauritius to investigate different techniques adopted by the development teams for capturing and sharing the knowledge acquired.

Ticketing & CS System Development For Industrial Needs

TLDR
The design and development of a web-based ticketing and customer support system for the IT consultant company PT Mitra Mentari Global (MMG), aims to build a system that can aid customers of PT MMG in submitting any problem or complaints they might have when using PT M MG’s products in the form of a support ticket, while also helping the employees in handling and organizing those complaint tickets from customers.

References

SHOWING 1-10 OF 50 REFERENCES

The secret life of bugs: Going past the errors and omissions in software repositories

TLDR
Results show that the histories of even simple bugs are strongly dependent on social, organizational, and technical knowledge that cannot be solely extracted through automation of electronic repositories, and that such automation provides incomplete and often erroneous accounts of coordination.

CVS integration with notification and chat: lightweight software team collaboration

TLDR
There is evidence of the tool transforming archival log entries into communicative acts and supporting timely interactions, which has implications for consideration of more lightweight solutions for supporting collaborative software development, as well as managing awareness and interruptions more generally.

Let's Talk About Bugs!

TLDR
The analysis of testing at Foss Electric resulted in the identification of the need for computer support for coordinating this part of the software testing process, e.g., support of distributed classification, routing of information, and facilities providing an overview of state of affairs.

What Makes a Good Bug Report?

TLDR
The CUEZILLA prototype is a tool that measures the quality of new bug reports and recommends which elements should be added to improve the quality, and discusses several recommendations for better bug tracking systems which should focus on engaging bug reporters, better tool support, and improved handling of bug duplicates.

An Overview of the Software Engineering Process and Tools in the Mozilla Project

TLDR
The software engineering aspect of a large Open Source project is described and the software engineering tools used in the Mozilla Project are covered, since the Mozilla process and tools are intimately related.

People, organizations, and process improvement

TLDR
The authors report on two experiments to discover how developers spend their time and describe how noncoding activities can use up development time and how even a reluctance to use e-mail can influence the development process.

"A Bug's Life" Visualizing a Bug Database

TLDR
This paper proposes two visualizations to render bugs as first-level entities in bug tracking systems, which store data about the problems that various people, from developers to end users, detected and reported.

Who should fix this bug?

TLDR
This paper applies a machine learning algorithm to the open bug repository to learn the kinds of reports each developer resolves and reaches precision levels of 57% and 64% on the Eclipse and Firefox development projects respectively.

Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing

TLDR
Managing the Testing Process shows how a bug-tracking database is the most effective model for managing the testing cycle and presents dozens of tips for succeeding in the software Q/A job market.

Supporting change request assignment in open source development

TLDR
A study on how change requests have been assigned to developers involved in an open source project and a method to suggest the set of best candidate developers to resolve a new change request are proposed.