In a previous post, we explained how to integrate Ctrlflow Automated Error Reporting with an external bug tracker. Since then, we have added GitHub to the list of supported bug trackers. This allows reviewers to create bugs from within the Ctrlflow Automated Error Reporting UI and have problems synchronized with their corresponding [...]Ctrlflow
The Ctrlflow blog covers insights about Automated Error Reporting & Code Search for Java in Eclipse, including exception handling, code snippets, bug tracking, etc.
Ctrlflow Automated Error Reporting recently introduced project dashboards, whose detailed charts make it easy to track how effective projects are at fixing problems. With the introduction of dashboard queries, these dashboards have become even more useful. For every project, you can define one or more custom queries, which will be [...]Ctrlflow
Ctrlflow Automated Error Reporting now comes with a much requested feature: charts and dashboards. At the moment, you can choose from a dozen different chart types. These range from a simple pie chart showing the severity of reported problems to an elaborate scatter plot showing which of your projects are best at fixing problems. This [...]Ctrlflow
TL;DR This article describes four standard workflows by which you can quickly and effectively analyze and process incoming problems. As a rule each error report falls into one of the following 4 categories: Known Bug: The user reports a problem that the team already knows about and which is already tracked in the bug tracker. [...]Ctrlflow