Why Common Code switched to BugHerd

Why Common Code switched to BugHerd

We recently caught up with Stephen Neville Co-Founder of Common Code to check how their switch to BugHerd was going. Here's what Stephen had to say ...

Chanie Hyde


May 10, 2012

Case Study|||

We recently caught up with Stephen Neville Co-Founder of Common Code to check how their switch to BugHerd was going. Here's what Stephen had to say:

Q: Tell usabout Common Code

Stephen: Common Code is a collective of application developers. We specialise in Django/Python and related technologies.We have been up and running for about 6 months now. Things are going pretty well so far and we are up to about 10 people all up.The best way of describing us is we offer an insourcing solution of sorts where we provide application development teams to our clients. They can either be managed directly by the client or we can manage projects ourselves.Currently we are working with Cotton On, Kogan and a few others:


Q: Why did you start using BugHerd?

Stephen: BugHerd gives us the ability to easily track and manage bugs without having to get too complicated. It's particularly easy for non-technical people to understand and be involved in the process.

Q: What did you use previously?

Stephen: A combination of stuff depending on the kind of bug. We have definitely received the odd marked up MS paint or powerpoint file also.

Q: How does this differ with BugHerd?

Stephen: BugHerd it makes it much easier to collate and manage bugs in one place and allows us to extend the reporting team outside of technical staff and into the wider business of our clients.

Q: What features would you like to see added?

Stephen: I think the ability to replicate technical errors would increase the value significantly. At the moment it is mainly limited to display level bugs.

Recent articles

Want more resources like these? Subscribe to the BugHerd Blog 📥

✅ Subscribed!
😕 Oops! Something went wrong while submitting the form.