It would have to cleanly and simply manage all of the different needs that small teams have: bug tracking, issue tracking, feature requests, prioritization, cod

It would have to cleanly and simply manage all of the different needs that small teams have: bug tracking, issue tracking, feature requests, prioritization, code changes, etc. My rule of thumb for switching to new tech is that the new app must be a 10x improvement over the old app, whether that's 10x cheaper, 10x faster, 10x features, or however I wanna measure it. If it's not that much better, then the paperwork/training hassle isn't gonna be worth it for my team to switch. One example is the Hipchat/Slack discussion. We used Hipchat before Slack was a thing. Slack looks awesome. But is it 10x more awesome than Hipchat? I've never been convinced, and it's just not worth the hassle of setting everyone up with Slack accounts and software for the incremental improvement. Right now, bug tracking is tedious but manageable. You need to make it 10x easier, 10x cheaper, or 10x more features (or some smaller combination thereof) in order for people to consider it a no-brainer to switch. And to be honest, that's a tall order. You risk turning into a Salesforce-esque nightmare where you're trying to do everything at once. If you could somehow unify one or two of those things into one coherent, easy to use app (a la Zenefits or Workday or ZenPayroll), then you'd be on the right track. Good luck!