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."Jira is very user friendly, easy to install, and easy to access."
"Everything is tracked in one place."
"We have the best community to support any problems that we have."
"The most valuable feature is the full integration between Work management, Source code management, and Test Automation."
"Jira has been a good l tool for collaborating across large groups of people. The JQL feature is powerful and easy to use."
"Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product."
"We do not have a lot of time for investigating new things, but Jira has saved us a great deal of time. It has a nice user interface and we can do a lot of things with it."
"The features that we find most valuable are the Workflow, Scrum workflow, and Dashboards."
"I feel that the test plan and test tools are more manageable in TFS."
"We use TFS for forecast management."
"The biggest value-add is the solution integrates well with most Microsoft products."
"The most valuable feature of TFS is integration."
"It's user friendly. We haven't had any issues so far. It's flexible. If we need something, we can always contact the owner in our headquarters to make a configuration."
"The interface is easy to navigate."
"I like the build management features and the integration with Jenkins and many other tools."
"This solution enables us to link all items usefully, in the way we use Agile."
"The automation feature needs to be more user-friendly."
"Sometimes, it is slow and hangs. We faced some stability issues where JIRA was down for a day. Also, we have lost some of our comments made in the JIRA because of downtime."
"I'd like the solution to be more secure."
"Jira's collaboration and integration with other apps and tools could be improved."
"Lacks field-level permission in the cloud version."
"I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues."
"We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product."
"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."
"I'd like to see some kind of visualization tool for TFS that would make life much easier."
"More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively."
"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."
"The manageability and performance of the product are areas of concern where improvements are required."
"Microsoft should discontinue the use of SharePoint as I don’t really see any value add to TFS, document management features can be included in TFS web portal itself, if required!"
"Since the TFS was an on-prem solution, the private network accessibility was restricted."
"The solution is stable but could improve."
"It would be better if we could bring it out on the cloud."
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, TestRail, OpenText ALM / Quality Center and Visual Studio Test Professional. 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.