Ctrlflow Blog

Categories


Recent Posts


Track Bugs at GitHub with Ctrlflow Automated Error Reporting

CtrlflowCtrlflow

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 GitHub issues.

This post tells you how setup GitHub as an external bug tracker. It also highlights how using GitHub differs from using Ctrlflow Automated Error Reporting with other bug trackers like Bugzilla and JIRA.

Setting up GitHub as an External Bug Tracker

To setup GitHub as the Ctrlflow Automated Error Reporting server’s bug tracker, you have to supply credentials for the GitHub account you wish to track problems in.

Go to Settings > Bug Tracking and select GitHub as the account’s system. As the base URL choose your account’s URL, e.g.,“https://www.github.com/example”. For the bug URL, use the same URL, but add “/{0}” to the end. Provide the account’s email and password and save the changes. Finally, click both the Import Problem Settings and Synchronize Projects buttons in turn.

IMPORTANT!
Note that you don’t specify the repository to use here, only the account. Ctrlflow Automated Error Reporting maps all repositories of an account to projects, allowing bugs to be created in the issue tracker of the appropriate repository.

bug-tracking-settings-githubThat’s it! From now on, reviewers can create bugs for problems and have them linked with GitHub.

Adapting to GitHub’s Workflow

GitHub’s issue tracker has a different workflow than Bugzilla or JIRA. Ctrlflow Automated Error Reporting thus adapts to that workflow by not syncing a problem’s severity or resolution, as these two concepts do not exist in GitHub. Instead, it is customary in GitHub to use labels to categorize and prioritize issues. Thus, Ctrlflow Automated Error Reporting automatically syncs labels with the server as tags (with a prefix of “github-”).

github-problem-status

Of course, you can use tags when constructing search queries, automated actions, or problem digests. This allows you to create advanced workflows. For instance, you can setup automated actions that reopen problems which are believed to be fixed should they occur in newer versions.

If you want to learn more about using Ctrlflow Automated Error Reporting with external bug trackers, read on.

Ctrlflow Automated Error Reporting

Learn more about all features