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's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable."
"JQL, JIRA Query Language enables me to filter all the issues, display the items as I want."
"Provides good output and is user-friendly."
"Its visual display and ease of use are most valuable."
"What I find valuable about Jira is that it's an ecosystem. Sometimes, it does not provide the best in class solutions, but it's so well integrated. You will not have many problems with integration."
"Jira is very user friendly, easy to install, and easy to access."
"There are a couple of things that I find valuable about Jira, the first being its architecture. For instance, I like that you can create dashboards easily, which makes it very user-friendly. You don't need much training on that. You can just get right to it and people are able to use almost all of Jira's features with little training."
"It's easy to escalate the issues to the product development team."
"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."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"Work item management integration with source control."
"Stability is okay."
"This solution enables us to link all items usefully, in the way we use Agile."
"The most valuable feature of TFS is that it keeps the code secure while working collaboratively in a team of four or five individuals."
"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."
"It's is a very stable solution."
"Its UI can be improved a little bit. I know this a business tool and not a commercial tool, but it could be a little bit more interactive like the HP ALM/Quality Center, which provides you the results of graphs and gives you a lot of visual representations. I feel Jira lacks a little bit in this aspect."
"The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything."
"Once a story is closed, all the records, versions, and documentation associated with it are gone. We lose the traceability of what was done."
"Tracking is important but the built-in features don't meet our needs."
"This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number."
"One major issue that I, and even our business stakeholders, have noticed is related to Epic Link. When Epic Link's background color is a dark color, it effectively becomes unreadable. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view."
"For our company, we're thinking about not only project management solutions but also collaboration solutions, and maybe if Jira had a chart or quick commenting option, it would be great."
"There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there."
"As an end-user, I expect the solution's performance to be faster while staying as stable as possible."
"Since the TFS was an on-prem solution, the private network accessibility was restricted."
"It would be better if we could bring it out on the cloud."
"The test management interface is not very handy."
"The tool needs improvement in stability."
"The user interface could be improved to make it simpler and increase usability."
"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!"
"Access and permissions are confusing when attempting to include basic manual testing functionalities."
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.