We performed a comparison between Jira and TFS based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features of this solution are workflow and reporting."
"The customization and tailoring of the workflows have proven to be very useful."
"We have the best community to support any problems that we have."
"The feature that I have found most valuable is that it is a quite powerful user tracking system."
"It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it.."
"The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on."
"It is easy to integrate Jira within our current IT environment. Jira has connectors and supports various integration."
"The product's initial setup phase is easy."
"The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."
"The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager, and you can have everything that is related to a requirement attached to it."
"Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error."
"The most valuable feature of TFS is its compatibility with Microsoft Windows systems. We have predominantly Microsoft solutions and TFS work well."
"The solution's iteration board is good because you can track all your work with it."
"It's an integrated system that includes all the information that we need to deliver our products smoothly and to track the progress of each piece of code."
"Stability is okay."
"The most valuable feature is the backlog."
"If CI/CD is integrated with it, it would be better. I've used Azure DevOps before, and it's nice to have everything, such as CI/CD Repos and other things, integrated. Jira has fewer integrations. Azure DevOps has an easier interface, and it has got everything in one spot. I don't have to jump around in different applications."
"If you're not a technical person, it might not be very user-friendly."
"The hierarchy for Jira tickets is too flat."
"Adding applications is very expensive."
"This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number."
"The GUI should have much better features like more graphical illustrations. There are some cases or benchmarks that we are trying to capture into a dashboard GUI's graphical summary, but unfortunately JIRA is not able to do that."
"Sometimes the screens can be a bit too busy. There's often a lot of information on the screen. I think paring things down and applying some UX improvements might enhance the look and feel of the interface."
"I'd like the solution to be more secure."
"Since the TFS was an on-prem solution, the private network accessibility was restricted."
"More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively."
"The price could be cheaper."
"This solution is quite old and it is already being bundled as Azure DevOps Server."
"TFS's CI/CD, project pipelines, and management development could be improved."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"TFS on-premise does not support integration with SharePoint Online."
"The user interface could improve and test management was not useful in TFS."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 93 reviews. Jira is rated 8.2, while TFS is rated 8.0. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". On the other hand, the top reviewer of TFS writes "It is helpful for scheduled releases and enforcing rules, but it should be better at merging changes for multiple developers and retaining the historical information". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and ServiceNow Strategic Portfolio Management, whereas TFS is most compared with Microsoft Azure DevOps, Rally Software, Visual Studio Test Professional, OpenText ALM / Quality Center and TestRail. See our Jira vs. TFS report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.