JIRA vs. TFS
As of April 2019, JIRA is ranked 1st in Application Lifecycle Management (ALM) Suites with 29 reviews vs TFS which is ranked 3rd in Application Lifecycle Management (ALM) Suites with 28 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, Microsoft Azure DevOps and AgileCraft. TFS is most compared with JIRA, Micro Focus ALM and Microsoft Azure DevOps. See our JIRA vs. TFS report.
Add to compare
Most Helpful Review | |||||
|
| ||||
 Find out what your peers are saying about JIRA vs. TFS and other solutions. Updated: March 2019. 333,928 professionals have used our research since 2012. | |||||
Quotes From Members
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
Pros | |
This tool can be used anywhere and on any device. It has an easy UI that can easily plug-in to every level. Some of the features that are most important to me of JIRA Agile are the sprint planning, being able to write user stories and being able to use task management. 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 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. 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. |
Cons | |
The user interface and views on different devices should be improved. The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable. I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down, and I had a number of users that could not use the tool. 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 dashboard needs more enhancements. 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. |
Pricing and Cost Advice | |
We feel that the product is a good value for the cost. 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. |
 Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs. 333,928 professionals have used our research since 2012. | |||
Answers from the Community | |||
See all 21 answers » | |||
Ranking  | |||
Views 90,872 Comparisons 47,318 Reviews 27 Average Words per Review 329 Avg. Rating 8.1 | Views 40,973 Comparisons 22,388 Reviews 28 Average Words per Review 361 Avg. Rating 8.4 | ||
Top Comparisons | |||
 Compared 27% of the time. Compared 18% of the time.  Compared 8% of the time. |  Compared 61% of the time.  Compared 6% of the time. Compared 5% of the time. | ||
Also Known As | |||
| JIRA Software | Team Foundation Server | ||
Learn | |||
| Atlassian | Microsoft | ||
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. | ||
Offer | |||
Learn more about JIRA | Learn more about TFS | ||
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 | ||
Top Industries | |||
Software R&D Company16% Healthcare Company13% Financial Services Firm13% Insurance Company13% Financial Services Firm22% Manufacturing Company19% Comms Service Provider11% Healthcare Company9% | Financial Services Firm43% Manufacturing Company14% Software R&D Company10% Retailer10% Manufacturing Company18% Financial Services Firm17% Government9% Insurance Company9% | ||
Company Size | |||
Small Business33% Midsize Enterprise19% Large Enterprise48% Small Business12% Midsize Enterprise14% Large Enterprise73% | Small Business14% Midsize Enterprise23% Large Enterprise63% Small Business5% Midsize Enterprise12% Large Enterprise82% | ||
Find out what your peers are saying about JIRA vs. TFS and other solutions. Updated: March 2019.
333,928 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 25000+ 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 25000+ 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.
Both products share a decent amount of market share. I prefer the use of TFS when conducting .NET development due to the ease of use with the Microsoft IDE. If this is the primary basis of the development effort - perfect. If on the other hand the development is spread across a variety of languages & technologies, or the development landscape is varied and primarily open, JIRA becomes the platform of choice. TFS seems great in small team settings, while JIRA seems more easily applied to large, distributed development teams.
The best comparison would be Atlassian toolset Vs TFS. What is covered in TFS can be covered with the different Atlassian tool sets. The integration between the different Atlassian tools is quite seamless but you are not bound. Most tool sets provide an integration with Jira. For great automation I appreciate the Jira (Atlassian) ecosystem. There are several plugins that cover most needs. However other issues such as your current needs,skills, budget, company size and tools should be taken into consideration. And the best ROI is to get the free versions and try them out both can do the Job and even Microsoft shops developing with Visual Studio can easily integrate with Atlassian tools.
Both are good, it depends on your operation and requirements.
1. Are you looking for flexibility interface? If so, JIRA is easier to use than TFS.
2. Are you looking for Reports Analytics? Again, JIRA is better than TFS.
Jira is a "great to integrate" part(!) of an ALM solution. VSTS (cloud) and TFS (on-prem) are much more complete because they already provide version control, work item management, reporting, continuous integration, continuous delivery, wiki, manual and automated test, ...
I would always prefer to use VSTS over TFS over Jira because VSTS does always include the newest features from VSTS/TFS, but both provide a much more complete solution than Jira and I don't want to spend my time to configure integration between different systems.
In the past (when working as a consultant), I migrated a Java-only-team to TFS and the only complaint was that the build system did not provide a way to see the output of maven in real-time ... this has been fixed some years ago.
One important aspect is the know how that is available on the team. If you have great know-how with using Jira and how to integrate it with other ALM parts, it might be a better solution to go that way. If you are new to both, I would recommend TFS/VSTS because you will have a more complete solution with seamless integration of all parts in a shorter time.