Ctrlflow Blog


Recent Posts

Bug Tracking with Ctrlflow Automated Error Reporting


You can use Ctrlflow Automated Error Reporting in two ways. Either you use it as a minimal bug tracker for your error reports or you can use it’s Bug Tracker Integration in order to load the found problems into your company’s bug tracker. This article presents both possibilities to you.

How to use Ctrlflow Automated Error Reporting Server as a minimal bug tracker.

As in Bugzilla or Jira, all problems in Ctrlflow Automated Error Reporting have a status, a resolution, and a severity (see the red box in the image below). Every bug can be open, closed or prioritized just like in a normal bug tracker and so bug fixing workflows can map easily to Ctrlflow Automated Error Reporting. The list of statuses, resolutions and severities can be configured and aligned with your own individual workflow.


Each Problem in the Ctrlflow Automated Error Reporting has a severity, a status, and a resolution.

With Ctrlflow Automated Error Reporting you can immediately communicate the current state of a problem with someone who has just sent a report – and even before he actually sent it. For example, whether the problem is still open, or was already fixed, or whether you still need further information to fix the problem, such as steps to reproduce. Further information concerning this can be found in the “Talkback Settings of Ctrlflow Automated Error Reporting Server”.

How you can use an external bug tracker with Ctrlflow Automated Error Reporting

Often projects already have an existing bug tracker in which bugs, feature requests and similar are collected. In such cases it makes sense to collect and track the problems you find using Automated Error Reporting in this external bug tracker.

Therefore you can create a bug in your bug tracker out of every problem found. To do this you should click on “Create new bug report” in the Bug Tracker Menu on the Problem page. In the next dialog you can select the bug project, the bug component and the version and, if necessary, you may include a few other fields of information. After clicking “Create Bug” the bug report will be automatically created in your bug tracker and will be linked with the problem.


If enough information is collected to triage and fix the problem, you can turn it into a bug report in your external bug tracker in just two clicks…


The Create Bug Dialog. Pressing on “Create Bug” creates the bug report in your external bug tracking system.

You can control how your Bug Reports will look and which information will be included in them with Ctrlflow’s Bug Templates. Check the “Bug Tracker Settings“ for further details on this topic.

My bug tracker & Ctrlflow Automated Error Reporting  Server- two websites with different data?

No. As soon as you track a problem in your primary bug tracker, the Automated Error Reporting Server will disable the status, severity and resolution fields and instead pull these values directly from your bug tracker. So your data will always be in-sync with your bug tracker.

You shouldn’t immediately load every problem into your bug tracker. Often it will first make sense to first gather all necessary information (such as steps to reproduce) using Ctrlflow Automated Error Reporting and to only create a bug, when it is ready to be worked on.

Which bug trackers are supported?

Currently Ctrlflow Automated Error Reporting Server supports Bugzilla and JIRA. Let us know if your bug tracker is not currently on the list of supported bug trackers. If the bug tracker has an open API, we will add support for it in a few days.

Ctrlflow Automated Error Reporting

Learn more about all features