title: Reasons not to build your own bug tracking system
body: <p>Several times now I've been faced with plans from a team that wants to build their own bug tracking system - Not as a product, but as an internal tool.</p>
  
  <p>The arguments I've heard in favous are usually along the lines of :</p>
  
  <ul>
  <li>Wanting to 'eat our own dog food' in terms of some internally built web framework</li>
  <li>Needing some highly specialised report, or the ability to tweak some feature in some allegedly unique way</li>
  <li>Believing that it isn't difficult to build a bug tracking system</li>
  </ul>
  
  <p>What arguments might you use to support buying an existing bug tracking system? In particular, what features sound easy but turn out hard to implement, or are difficult and important but often overlooked?</p>