Author name: sharmil.desai@donedone.com

In the past, I’ve often wrestled with designing an optimal relational database model to represent users in a multi-tenant system. I’ve wanted to get the model just right—enough structure to accomodate future enhancements without bloating the schema with excessive JOINs, overly-wide tables, or any other number of typical relational-database “sins”. Over four years into our […]

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. In today’s final introductory post to DoneDone, we introduce release builds. When we first started using other issue tracking tools, we discovered

Last week, I talked about my experiences using DoneDone to manage household issues. To accompany my post, I wrote a simple Rails application to query data from the DoneDone API and display it on a publicly-accessible dashboard. Today, I’d like to walk through the process of building that application from the ground up. If you’d

Steal this bug tracking template that includes bug tracking best practices, how to define the bug tracking life cycle and a repeatable workflow you can use.

Three bug tracking best practices you should always follow when creating a workflow for your small business. Save time and headaches.

Uncover how breaking down silos can revolutionize email-sharing strategies for ecommerce support teams. Enhance collaboration & customer experiences.

Discover the art of ‘Eating an Elephant’ in project management with DoneDone. Learn how to tackle large projects by breaking them into manageable tasks, prioritize effectively, and maintain momentum with our friendly, approachable guide. Achieve project s

Nine months into selling our first web-based product, DoneDone, we’ve learned a lot of lessons. Bugs, even the most hidden and seemingly dormant, are eventually found because people are using your product all over the world at all different times of day. One of the big lessons we’ve learned is how we program against third-party

Last Friday we released Git and Subversion integration for two fantastic version control services, GitHub and Beanstalk. What this means is that programmers can make a number of changes to DoneDone issues directly from their version control tools (Cornerstone, Tortoise, command line, etc.), provided their repositories are hosted at one of the above services. We