One of the most requested features by our users was extension for Google Chrome. We’re please to say that BugDigger extension for Chrome has been released a week ago. You can get it from add-ons download page.

We’ve also released BugDigger plugin for JIRA version 1.3.1 that adds support for the Chrome extension and fixes some smaller issues. The plugin can be downloaded here and upgrade is free.

We are pleased to announce a standalone BugDigger plugin for JIRA coming out next week. Take a peek:

About the same time we released BugDigger few months ago we started receiving questions about our plans to support issue tracker A or B (you name it). We’re aware that there are many popular issue trackers out there (and even more internal, custom solutions) but we can’t make everyone happy. Well… at least not at once.

Today we’re pleased to announce the first release of our issue tracker integration API that should be the main guide for any software developer writing a BugDigger plugin for its favorite bug tracker. (Support for the API is already live and serving.)

If you use an issue tracking software that is not supported by BugDigger, we encourage you to invite its developers to make a plugin implementing our simple API. We’ll be glad to help if there’s any question or issue on the way.

We have been quite busy, working on BugDigger for the last 4 weeks. In addition to many small improvements, we have a few major additions to announce:

Support for Basecamp

Basecamp is a very popular project management and collaboration solution, but it has no “standard” issue tracking features. However, Basecamp’s To-Do lists can be used for this purpose with equal success. When submitting a bug to Basecamp, BugDigger will automatically create a new to-do item in the list named after the page for which the issue was created. [more info]

Support for FogBugz

FogBugz is a classical issue tracker and project management solution, and we’re pleased to offer support for it. [more info]

Listing Bugs by Application Controller

BugDigger analyzes the URL of a “faulty” page and adds the bug report to the class of reports with a similar path. We’ve added shortcuts to the bug details page, so now developers can easily list all bug reports related to the same application controller.

(We did our best to implement automatic classification of URLs, recognizing the most common patterns, but we’re aware it’s not perfect and that it may not work well for every project. We plan to improve this further in the following weeks.)

We hope you’ll enjoy the new features. Let us know what you think!

We’re very excited today. After several months of development and beta testing, BugDigger service is finally going live!

The initial release of BugDigger allows users to easily capture bugs in their web applications and send them to an external bug tracker. Bug reports submitted via BugDigger include:

• The browser and version number used
• The URL where the issue occurred
• Recently opened URLs
• Screenshot of the web page

Automatically captured screenshot can be further edited using built-in Flash-based image editor.

Beside integrating with more external services, we have a bunch of new features we’d like to implement in the following months. What’s more important is we’d like to have your feedback on what we’ve done so far and which features you’d like to see in BugDigger.