JIRA vs. TFS
JIRA is ranked 1st in Application Lifecycle Management (ALM) Suites with 21 reviews vs TFS which is ranked 4th in Application Lifecycle Management (ALM) Suites with 27 reviews. The top reviewer of JIRA writes "Helps us work in Agile and Scrum formats across multiple locations and time zones". The top reviewer of TFS writes "Can Provide A Centralized Place To Store All Source Code And Build Information For Entire Organization". JIRA is most compared with TFS, Micro Focus ALM and IBM Rational Team Concert (IBM ALM). TFS is most compared with JIRA, Micro Focus ALM and CA Agile Central. See our JIRA vs. TFS report.
+Add products to compare
Read 21 JIRA reviews. | Read 27 TFS reviews. |
Most Helpful Review | ||||||
|
| Use Null Product? Share your opinion. | ||||
 Find out what your peers are saying about JIRA vs. TFS and others in Application Lifecycle Management (ALM) Suites. 305,899 professionals have used our research since 2012. | ||||||
Quotes From Members Comparing JIRA vs. TFS
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:Pros | ||
Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on. It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasks We can cope with processes easily without adapting the tool, but adapting the tool to processes. The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components. JQL, JIRA Query Language enables me to filter all the issues, display the items as I want. 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. I found it super useful, as it is customizable for different teams and users. It improved communication, as it was a popular tool, and most people enjoyed using it. | From the project management perspective, the tool is efficiently managing teams by giving management information, such as reports, graphs, velocity, capacity, etc. The biggest value-add is the solution integrates well with most Microsoft products. Build definitions and releases within the product. allow us to put our latest applications in the field. It has great functionality: work items, backlogs, source code, build releases, and it's easy to use. Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error. Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology. I like its MTM (Microsoft Test Manager) section which gives us options to create various test plans and add test cases into it. The API for managing TFS programmatically is very powerful, you can listen on work items changes by TFS events. | |
Cons | ||
JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless. There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level. 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. There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes. I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice. The following definitely need improvement: UI, speed, and mobile app functionality. Out-of-the-box reporting is limited. It would be helpful if more customisation was possible. I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it. | More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively. Since it is Microsoft, it is technology agnostic, thus it does not really fit into various different technologies in the organization. We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS. TFS on-premise does not support integration with SharePoint Online. Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI. TFS and MTM have their own style of working and they are different from other tools like Jira or TestRail, which are simpler and easy to use. Sometimes we feel that it need more CPU, and RAMs on TFS server, either we implemented the hardware with the product minimum requirements. 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! | |
Pricing and Cost Advice | ||
I understand JIRA is quite expensive. It does not cost that much. Almost everybody uses JIRA nowadays because it is the most cost-effective solution. The licensing model is annoying. They nickel and dime you. It is very cheap if you forego the local instance and stick to the cloud. | It is pretty expensive compared to other project management tools. If running TFS on-premise is expensive, maybe you could consider moving to the Cloud and use the Visual Studio Team Services. Use the Microsoft recommended “seat-based” licensing model. This allows a single developer with multiple machines to consume only one client license. TFS is on the higher side, but if you intend to use the tool as a complete ALM tool, it will reduce your costs in the long run. It's just as expensive as HPE ALM, without many of the features, best used for development tool only to avoid higher costs. | Information Not Available |
 Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs. 305,899 professionals have used our research since 2012. | ||||
Answers from the Community | ||||
See all 20 answers » | ||||
Ranking | ||||
Views 77,621 Comparisons 43,908 Reviews 21 Followers 1,695 Avg. Rating 8.0 | Views 35,864 Comparisons 21,977 Reviews 27 Followers 1,282 Avg. Rating 8.4 | Unranked In Application Lifecycle Management (ALM) Suites | ||
Top Comparisons | ||||
 Compared 32% of the time.  Compared 16% of the time.  Compared 5% of the time. |  Compared 64% of the time. Compared 12% of the time.  Compared 5% of the time. |  Compared 39% of the time.  Compared 32% of the time.  Compared 29% of the time. | ||
Also Known As | ||||
| JIRA Software | Team Foundation Server | |||
Learn how it works | ||||
| Atlassian | Microsoft | Null Vendor Video Not Available | ||
Overview  | ||||
JIRA has multiple deployment options to provide the flexibility your organization needs. Cloud is a fully hosted service for customers who want to iterate quickly and have us take care of managing the infrastructure. For customers who need to run our applications behind their firewall, we have Server and Data Center options. Server delivers greater capacity for a larger user base and gives you more control, allowing you to remain compliant with your enterprise IT, security, IP and privacy policies. For our largest customers, Data Center provides all the capability of our Server option, along with high availability, instant scalability and performance at scale. Atlassian also offers premium support and strategic services for enterprise customers. Technical Account Managers are cross-functional technical advisors providing proactive planning and strategic guidance across your organization. Premier Support goes above and beyond our standard offerings to give you account-wide support from a team of senior support engineers. | Visual Studio Team Foundation Server (TFS) is the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution. TFS supports agile development practices, multiple IDEs and platforms locally or in the cloud and gives you the tools you need to effectively manage software development projects throughout the IT lifecycle. | Information Not Available | ||
OFFER | ||||
Learn more about JIRA | Learn more about TFS | Learn more about Null Product | ||
Sample Customers | ||||
| Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi. | Vendex KBB IT Services, Info Support, Fujitsu Consulting, TCSC, Airways New Zealand, HP | Information Not Available | ||
Top Industries | ||||
REVIEWERS 15% 15% 15% 12% VISITORS READING REVIEWS 21% 10% 7% 6% | REVIEWERS 43% 14% 10% 10% VISITORS READING REVIEWS 25% 16% 8% 5% | No Data Available | ||
Company Size | ||||
REVIEWERS 32% 18% 50% VISITORS READING REVIEWS 21% 18% 61% | REVIEWERS 14% 23% 63% VISITORS READING REVIEWS 10% 18% 72% | No Data Available | ||
Find out what your peers are saying about JIRA vs. TFS and others in Application Lifecycle Management (ALM) Suites.
305,899 professionals have used our research since 2012.
See also JIRA Reviews, TFS Reviews, and our list of Best Application Lifecycle Management (ALM) Suites Companies.
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.
Sign in to see all reviews and comparisons. It's free!
By clicking Sign in with LinkedIn™ you agree to let IT Central Station use your LinkedIn profile
and email address in accordance with our Privacy Policy and agree to the Terms of Service.
- Unlimited access to 22000+ reviews from real users
- Your own page to promote your professional skills
- Networking events and peer-to-peer consultations
Already a member? Sign in.
By registering, you agree to our Terms of Service and Privacy Policy.
- Unlimited access to 22000+ reviews from real users
- Your own page to promote your professional skills
- Networking events and peer-to-peer consultations
Already a member? Sign In.
We use both. It depends on your application and your budget.
For us, the Atlassian suite of tools required to do end-to-end ALM processing is very expensive (currency conversions also does not help). We, therefore, only use JIRA as an incident/support/planning tool.
We are a Microsoft partner and hence the VSTS/TFS tool suite is much more affordable to us. The visibility of this tool from backlog item to code, build test and released into production is amazing, but it lacks some of the basic admin capabilities that are well automated in JIRA e.g. as tasks are moved, the status of parent items/stories/epics are not automatically updated in VSTS. This adds a lot of admin overhead for product owners, scrum masters and team members.
If it weren’t for budget, the Atlassian suite will be my first choice. If you combine, JIRA, Bitbucket, and Bamboo you would get the same visibility.
We also use Confluence extensively as all our documentation are done Wiki style. We found SharePoint just becomes a repository and not a knowledge share platform.
Hope this helps!
Shout if you have questions.
Thanks for the information!
I have access to JIRA and TFS, but have used them very little making it difficult for me to provide any comparison. From an ALM perspective, I’ve been using IBM CLM instead with its Enterprise level Scaled Agile support for SAFe 4.5
If it's a Microsoft team I would defer to their preference. Otherwise, my own preference would be to use JIRA.
I would recommend using a modeling tool that architects and/or solution designers use. And use applications as objects on their drawings.
This would give insights on what applications are used more than others.
Once you have this insight then it becomes a matter of storing and using it either using Jira or TFS