Introducing Lighthouse Integration

by C.S. | 2012-02-07 |

Isn’t it wonderful when tech companies work with each other? This is synergy without any of the boardroom bureaucracy, just simple Ruby-on-Ruby lovin’

As some of you may know, Pay4Bugs was first conceived to fulfill an internal need. We needed to debug, and wanted a good platform to do so. Since then, we’ve developed Mobile Software Testing (we wrote apps), and integration with Basecamp (we love 37Signals). When there’s a need that can be resolved with some code, we do it.

Of course we can’t always be building just for ourselves. A client of Pay4Bugs recently requested integration with Lighthouse. So what are they? From the Entp website (the fine folks behind Lighthouse), Lighthouse is described as “a hosted ticket/issue tracking application that we built to handle our own product development in the most simple workflow environment we thought possible.” Sounds good to us.

So after a few days of coding, we’ve completed integration with Lighthouse. Now when you approve a bug, Pay4Bugs will automatically send the information over to Lighthouse via the API. Find bugs here, track it there. Synergy.

Know any other software that you want to see us integrate with? Let us know via the comments below.

Tag:, , Leave a comment

An Upgrade to the Pay4Bugs Basecamp API Integration

by C.S. | 2012-01-17 |

For people who use 37Signal’s Basecamp to manage their projects, and use Pay4Bugs to find bugs, we just upgraded our API integration to make the interaction between the two sites more seamless.

As we described previously, when you enter your Basecamp API key into your Pay4Bugs profile, every time you approve a bug, it’ll enter a to-do list item automatically in your Basecamp project. However we didn’t think that was enough, since the integration was only one way.

Now when you complete a to-do item in Basecamp, we send the information back to your bug list on Pay4Bugs. This way as soon as a bug is resolved, it’ll appear as “fixed”, making it easier for testers as they approach your project.

Got any productivity APIs that you think we should connect to? Chime in with the comments section below!

Tag:, , , , Leave a comment

Pay4Bugs Upgraded to Rails 3

by Larry | 2011-12-26 |

Everything looks the same, but as of a week ago, Pay4Bugs is now running on Rails 3 and Ruby 1.9. The past couple months, we’ve been porting the code base over and fixing bugs.  Thanks as always to Pay4Bugs Testers for keeping us on our toes and quickly pointing out any bugs that slipped through our internal testing.

Now that we’ve got the codebase up to date, Pay4Bugs customers can look forward to a number of new client requested features and refinements on an accelerated schedule.

Last Friday, we launched a new email digest feature for customers. By default, clients will no longer receive an email for every new bug.  We realize how annoying this was.  Instead, clients will receive daily summary emails on days when new bugs are submitted and weekly email summaries otherwise.  Miss the per bug emails? You can turn them back on by clicking My Info.

Tag:Uncategorized Leave a comment

Introducing Pay4Bugs Basecamp Integration – We’ll find the bugs, use Basecamp to track their annihilation.

by C.S. | 2011-11-16 |

We’re huge fans products by 37Signals, which helps small businesses and enterprises organize projects and contacts in “the cloud” with their various web applications. Their flagship product is Basecamp, the project management software that we use internally and have recommended to many of our friends and clients.

The fact that Ruby on Rails was actually a framework extracted from their work on Basecamp makes them that much cooler. Need more convincing? the creator of Ruby on Rails Heinemeier Hansson commissioned his own special edition Italian sports car , but I digress…

Therefore we’re thrilled to announce that Pay4Bugs has now integrated with the Basecamp API, creating the bug squishing tag team that’s designed to deliver results.

Here’s how it works it a nutshell:

  1. Developers create new software products that could benefit from real life testing and debugging. A Pay4Bugs project is created with a bounty. In the project settings, connect to Basecamp using the Basecamp API.
  2. Testers around the world step up to the challenge, and submit bug reports to the developer.
  3. The project manager vet the incoming bug reports. Legitimate bugs are approved, and the information is automatically sent into your Basecamp project.
  4. Track your open bugs via the awesomely simple “To-do” lists in Basecamp, and watch the developers squash bugs with epic efficiency.

Software bugs, meet your worse nightmare.

For more information on Pay4Bugs, visit Pay4Bugs.com. You can learn more about 37signal’s Basecamp at http://www.basecamphq.com

Tag:, , , Leave a comment

How to find your Basecamp API Token

by C.S. | 2011-11-11 |

Basecamp is a project management platform from 37Signals. Pay4Bugs clients can integrate their Pay4Bugs projects with Basecamp by entering their Basecamp API Token.

To find your token, login to your Basecamp account, then click on “My Info” on the top right hand corner. Scroll down past the contact information to a box labeled “Authentication tokens.” Click on the “Show your tokens” link and grab your unique API Token, which permits Pay4Bugs to send bug reports directly to your project t0-do list.

Tag:Howto Leave a comment