« Listen To Your Partners | Main | To Tweet »

September 08, 2009



You'll need to look into GMail's offline access capability, which stores local copies of mail, and make sure there's not an outside chance that you'd run into a synchronization issue when different people are accessing the same account.


What about reporting? Escalation of issues? and more...

I'd suggest going with a cheap option like Fogbugz or if funds are that tight, go with a free system already set up to do bug tracking...


I'm not saying this is what we'll do. I was just brainstorming whether or not GMail *could be* an adequate solution.


It's an interesting probability when thinking about it from a bug tracking standpoint. The main issue as mentioned is the actual tracking of the bugs as they are being worked on. Other than setting different labels for certain stages of a solution it becomes difficult for those who need to know what stage of bug reporting that particular issue is on and also ensuring that while working offline you can sync everything up amongst multiple users of the same account from different locations without running into syncing issues. I'd hate to be that guy who goes in and tries to fix the bugs and then because somebody else was already working on it simultaneously that the whole thing went to hell because I thought I was being helpful and somebody else was doing something simultaneously that screwed things up. It's an interesting possibility, just requires a little more thought and a few tweaks to the overall system to fix these important bug tracking issues.

Ken Noland

Actually, Google Wave looks perfect for bug tracking. It has all the features of google mail and it allows for live editing of documents. It also supports plugins to existing systems, so you cuold utilize your existing bug tracker with the addition of a plugin.


How about using Mantis?

It is free and easy to setup. I have mine running on an external server and can log form anywhere using the web interface.

Now Granted I haven't actually read your post just the header so if this suggest is irrelevant please disregard. :)



PS: It is totally awesome. Best bug tracking software I have used.


Ok reading your comments some more.

* Web based

* Labels, which are far superior to categories / folders

Maybe? Could be added in comments

* Excellent search

* Discussion history on bugs

* Quick / easy / familiar interface

* Supports attachments for screenshots etc

Describe a bug

Store the bug info

Categorize a bug

Assign a bug

Get a list of bugs assigned to me

Get a list of bugs assigned to all programmers that are less than 6 months old but only if they were assigned on a Friday (or some other complicated search)

Check I'm pretty sure

Comment on a bug

Close a bug

It also has this awesome summary page that shows oldest bugs who is closing their bugs. Who is assigning the most. Who is reasigning.. lots of goodies to check up on people and their bugs :)

But it sounds like the GMail thing could work if you were up for it. Let me know how that goes ;)


Jon Keto

The only drawback would be reporting. How can you track burndown rates? Besides the typical endless code, regress, find bugs, repeat process you would not have a good idea of whether your project is stabilizing by a certain end date. Only a number of searches + proper labelling would tell you whether you are trending downwards with pri 1 bugs. This is where the Google Wave + plugin suggestion would win above. Honestly, this would be awesome to see and a great POC for Google. I am sure they would be happy to hear of a small game company using it to manage bugs in an effective manner. Plus you could probably also use camtasia to do screencaps, convert to silverlight and them emded directly into your Google Wave discussions.

The comments to this entry are closed.