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.
"It is very configurable, and we can do whatever we want. Jira dashboards are also good, and we use them extensively. We also use the tracking mechanism extensively."
"The solution is stable and reliable."
"The most valuable feature of Jira is the project package for development."
"Jira has a good reporting system. It also has an API, so we can do all sorts of reporting."
"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."
"I have found Jira to be stable."
"The way we can define and customize the search queries for the tickets in Jira is most valuable."
"The design of the interface is clean and not too busy visually."
"We use TFS for forecast management."
"It is a stable solution."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"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."
"I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"The most valuable feature of TFS is that it keeps the code secure while working collaboratively in a team of four or five individuals."
"Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part."
"The interface is good with TFS."
"A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product."
"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."
"The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified."
"I don't know if it's the way it's deployed in the organization, but the interface we are provided is not as customizable as other tools. The multi-language report is not enabled in our installation. I don't really know if it's something related to the tool or our installation."
"The Jira dashboards could be more useful. The dashboards have good widgets but the comparison of data over time or extraction of trends from the data is not easy."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."
"An area for improvement in Jira is that it's not designed for test management. To use it for test management, you need an add-on or several add-ons, e.g. Xray or Zephyr."
"The solution's server for deployment needs to be improved."
"Overall, I think it would be useful to have something similar where Microsoft comes up with supporting concepts of scaling Agile in TFS so that clients don't have to look for a separate tool."
"We encounter issues with backups."
"Since the TFS was an on-prem solution, the private network accessibility was restricted."
"There's not automatic access to test case management and execution."
"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 tool needs improvement in stability."
"It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies."
Jira is a powerful cloud- and subscription-based application lifecycle and issue management solution. It is designed to aid users both in project management and in resolving any issues that arise at any point in the software development process. It is especially concerned with easing the ability of developers to collaborate.
Some of the ways that organizations can benefit by choosing to deploy Jira include:
Real-time notification feature. Users can set Jira so that it offers them notifications that contain critical information in real time. It can send users email notifications when pressing issues have been updated. They can also set it to notify them about tasks that may be due, or other similar events.
Reviews from Real Users
Jira is a powerful solution that stands out when compared to many of its competitors. Two major advantages it offers are its workflow engine and its highly customizable dashboard.
Bharath R., the tool implementation and project management lead at a financial services firm, writes, “I feel the strongest feature of Jira is its workflow engine. It empowers us to automate our workflows within our organization. It's the one characteristic of Jira which I think can help any organization, be it in any domain.”
Uday J., a staff engineer at a computer company, says, “Another thing that I like a lot about Jira is that in the dashboard, you can plug the modules that you want. You can enable certain sections. For example, you can show trend history, open Jira tickets, etc. Some of the managers have created a dashboard for each engineer.”
Visual Studio’s Team Foundation Server (TFS) is a powerful application development lifecycle management solution. It aids developers in managing every aspect of their DevOps and application creation. TFS combines many different types of solutions into a single powerful platform.
Visual Studio TFS Benefits
Some of the ways that organizations can benefit by choosing to deploy TFS include:
Visual Studio TFS Features
Source code management. TFS comes with all of the tools that developers need to completely manage their source code. They can share their code so that multiple developers can work on the same project. Additionally, TFS enables them to do things like review the history of a particular piece of source code.
Reviews from Real Users
TFS is a highly effective solution that stands out when compared to many of its competitors. Two major advantages it offers are its source code management capabilities and its powerful integration suite.
Carl B., the vice president of engineering at Vertex Downhole Ltd, writes, “The most valuable features are related to source code management. Using TFS for source code management and being able to branch and have multiple developers work on the same projects is valuable. We can also branch and merge code back together.”
Ashish K., the principal consultant at Wipro, says, “I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well.”
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 57 reviews while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 25 reviews. Jira is rated 8.0, while TFS is rated 8.0. The top reviewer of Jira writes "Great reporting with lots of useful dashboards and excellent flexibility". 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, Polarion ALM and Microsoft Project, whereas TFS is most compared with Microsoft Azure DevOps, Visual Studio Test Professional, Rally Software, OpenText ALM / Quality Center and Zephyr Enterprise. 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.