This is the final post in a five-part series introducing DoneDone, our simple, straightforward issue tracking tool to finish projects strong. Sign up for a 30-day free trial or paid account at http://www.www.getdonedone.com.

This is the third in a five-part series of articles introducing DoneDone, our simple, straightforward issue tracking tool to finish projects strong.

This is the second in a five-part series of articles introducing DoneDone, our simple, straightforward issue tracking tool to finish projects strong.

This is the first in a five-part series of articles introducing DoneDone, our simple, straightforward issue tracking tool to finish projects strong.

Beginning Monday, I'll be starting a 5-day blog post series introducing DoneDone, our simpler, smarter issue tracking tool (and it's all web-based).

In a few short weeks, We Are Mammoth will be launching its first product, DoneDone. I've talked about it in three previous blog posts, under the code name BugSpray.

In a post last week, I discussed 3 ways that I'm improving the bug tracking experience with our internal bug tracking tool (codename BugSpray).

Bug tracking tools can be fairly simple from a programming perspective. Which is probably why there are hundreds of them out there all doing an equally OK job.

For the last couple months, I've been working on a bug tracking system for WAM that I expect will replace our current system in the coming months.