Which is better for comprehensive ALM: JIRA or TFS 2012?

Hey everyone,

I’m looking for advice on picking a full ALM system for our company. We’re trying to decide between TFS 2012 and JIRA. We need something that’ll work for our product, project management, QA, support, and dev teams.

The main features we’re after are:

  • Bug tracking
  • Workflow management
  • Project graphs (like bug counts and burndown charts)

Has anyone used both? What are your thoughts? I’m curious about how they compare in terms of features and price.

From what I’ve seen, TFS seems to play nicer with Visual Studio, but not so much with Eclipse. Is that right?

Any input would be super helpful. Thanks!

As someone who’s worked with both JIRA and TFS 2012, I can say they each have their strengths. In my experience, JIRA edges out TFS for comprehensive ALM, especially if you’re not heavily invested in the Microsoft ecosystem.

JIRA’s flexibility is a game-changer. I’ve seen teams customize it to fit their exact needs, from simple bug tracking to complex workflows across multiple departments. The reporting capabilities are top-notch too - creating custom dashboards and reports is much more intuitive than in TFS.

That said, TFS 2012 isn’t without merits. If your team primarily uses Visual Studio, the integration is seamless. But for mixed environments or teams using various tools, JIRA’s extensive plugin ecosystem is hard to beat.

Cost-wise, it really depends on your scale and specific requirements. I’d recommend trying out both if possible before making a final decision. The right choice often comes down to your team’s specific workflow and tech stack.

both r good but jira wins for me. more flexible, better for agile teams. tfs is grt with microsoft stuff but kinda limiting. jira’s reporting is awesome, customizable workflows rock. pricing depends on ur setup. if ur not all-in on MS, go jira. just my 2 cents

I’ve used both JIRA and TFS 2012 extensively in different enterprise environments. While both are robust ALM solutions, JIRA offers more flexibility and better support for third-party integrations. This makes it particularly adaptable to various development methodologies, with superior customization options for workflows and reporting.

TFS 2012 integrates well with Microsoft products but can be rigid for teams using a diverse tech stack. In your case, if flexibility and intuitive reporting are priorities, JIRA would be a strong choice despite TFS’s advantages within the Microsoft ecosystem.