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 solution provides users with clarity in terms of the scope of work in a given timeframe."
"The most valuable feature is project management."
"We've found the scalability to be good."
"Offers a common language set so we can bring people into projects and get them up and running almost immediately."
"A stable solution with no unplanned downtime."
"There are a lot of plugins in Jira and we purchase the ones we need."
"It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories."
"It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
"Work item management integration with source control."
"Stability is okay."
"From the project management perspective, the tool is efficiently managing teams by giving management information, such as reports, graphs, velocity, capacity, etc."
"Basically, the capacity to construct various products is something I find handy."
"I like the build management features and the integration with Jenkins and many other tools."
"The solution's iteration board is good because you can track all your work with it."
"The interface is good with TFS."
"It is a stable solution."
"Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management."
"There should be a way to look for specific comments. When we have thousands of comments on a Jira ticket, there is no way to look at the comments of a specific type. In the comments, if there is a way to put a tag, it would be helpful. For example, when there are a lot of lengthy discussions happening on a particular ticket, there could be a conclusion tag or something like that to indicate a conclusion. It would help in sorting the comments based on a certain category, such as conclusion."
"Jira is a little bit old fashioned, it could be more user friendly."
"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."
"In terms of the general Jira software, one element that is missing is budget management. Perhaps such functionality exists in add-ons, however."
"I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira."
"Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see."
"The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me."
"The overall reports in TFS could improve. Additionally, there should be an easier way to migrate from an older version to a newer one."
"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."
"Integration from Visual Studio could be improved."
"The program and portfolio planning facility can be improved."
"In the next release, I would like them to include integration for various projects, similar to what JIRA has, and they could create this feature on the dashboard."
"The test management interface is not very handy."
"The reporting functionality is something that they should work on."
"The usability of TFS is not that great."
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.