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."Offers a common language set so we can bring people into projects and get them up and running almost immediately."
"The integration is nice. We can integrate with TeamViewer and many more solutions. We need to go into Jira to complete the secure software delivery."
"The integration between Confluence and Jira, along with Jira's ticketing system, is a valuable feature the product offers its users."
"It is a stable solution, and we have had no issues with stability."
"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."
"Being able to automatize the deployment of the solution has been great."
"The JIRA user interface looks great. It's an overall good experience. It's very intuitive in the sense that you understand how it's going to work. It's very self-explanatory, and it's beneficial overall."
"The most valuable feature of Jira is that it's a well-known tool that many people are familiar with."
"We use TFS for forecast management."
"The initial setup is fairly easy."
"The solution's iteration board is good because you can track all your work with it."
"Microsoft's technical team is supportive."
"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."
"Work item management integration with source control."
"The most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful."
"The biggest value-add is the solution integrates well with most Microsoft products."
"It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great."
"Its search and reporting can be improved. They are already nice, but they can be further improved."
"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, 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 want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"The next-generation software projects lack a lot, and I found quite a few bugs. There are some really basic things that you still cannot do. For instance, to put a mandatory due date for a task that you create in one of these projects is still not available. That's a bit of a block because people, especially those who are not technical, are not going to add anything if it's not mandatory. It's going to be difficult to teach them that they should do it anyway."
"If you're not a technical person, it might not be very user-friendly."
"Of course, the price could always be cheaper."
"As an end-user, I expect the solution's performance to be faster while staying as stable as possible."
"The interface can be improved and made more user-friendly."
"The dashboard needs more enhancements."
"Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI."
"The reporting functionality is something that they should work on."
"One of the areas that could be improved is to have an effective full lifecycle management."
"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."
"We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and 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.