Compare JIRA vs. TFS

JIRA is ranked 1st in Application Lifecycle Management (ALM) Suites with 32 reviews while TFS is ranked 6th in Application Lifecycle Management (ALM) Suites with 8 reviews. JIRA is rated 8.2, while TFS is rated 8.2. The top reviewer of JIRA writes "Helps us work in Agile and Scrum formats across multiple locations and time zones". On the other hand, the top reviewer of TFS writes "Facilitates team collaboration and integrates well with other tools". JIRA is most compared with Microsoft Azure DevOps, TFS and AgileCraft, whereas TFS is most compared with JIRA, Microsoft Azure DevOps and Micro Focus ALM. See our JIRA vs. TFS report.
Cancel
You must select at least 2 products to compare!
JIRA Logo
Read 32 JIRA reviews.
64,510 views|55,853 comparisons
TFS Logo
Read 8 TFS reviews.
27,590 views|23,203 comparisons
Most Helpful Review
Anonymous User
Find out what your peers are saying about JIRA vs. TFS and other solutions. Updated: September 2019.
372,124 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
Transparency of development projects, as well as approval processes for some business projects, has improved massively.The most valuable feature of this solution is the source linking on the commit level to git.This solution assists us with being able to quickly and easily start sprints and keep accurate track of them, including billing using a time-tracking add-on.The most valuable feature is the Burndown Chart to see work that is outstanding.The most valuable features are the customized Dashboard, Sprint Planning, and Automatic Notifications.The most valuable feature is the full integration between Work management, Source code management, and Test Automation.The features that we find most valuable are the Workflow, Scrum workflow, and Dashboards.The most valuable feature is the flexibility of the configuration, being able to configure it to suit your own needs.

Read more »

I like the build management features and the integration with Jenkins and many other tools.I like the Kanban board. It is very useful in terms of seeing who is working on what and what the current status of work is.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.

Read more »

Cons
My main concern is the administration of projects, especially user groups, and this requires root access rights but there is no concept of layered admin rights.Backlog pruning and visualization are poor.The permissions can be challenging to get right.The reporting needs to be improved.This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number.The hierarchy for Jira tickets is too flat.It would be very useful to have drag and drop time tracking.The plugin management needs a lot of work.

Read more »

One of the areas that could be improved is to have an effective full lifecycle management.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 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.

Read more »

Pricing and Cost Advice
To try this solution, use their cloud offering to get familiar. After that, it's in my view worth the money.Licensing is on a monthly basis, and it is based on what you use.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.

Read more »

It is pretty expensive compared to other project management tools.

Read more »

report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
372,124 professionals have used our research since 2012.
Answers from the Community
Nurit Sherman
Claudette SteynbergUser

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.

13 March 18
Rene De VleeschauwerVendor

First of all Jira is not an ALM solution. Yes it is part of it, but his main task is issue mgt.

The corresponding TFS feature are TFS workitems.

For real ALM you need to start from requirements, dev environment , versioning, build, quality assurance and finally production.

If you are a pure Microsoft shop go for TFS, if not Jira might be a better choice (for issue tracking..)

13 March 18
Senior Manager of Infrastructure at a retailer with 10,001+ employeesReal User

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.

19 March 18
Peter NtendeReal User

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.

15 March 18
Anita WallVendor

Jira alone does not provide all the capabilities of an ALM; typically it will integrate with an ALM solution such as Zephyr or Micro Focus ALM in order to provide ALM-type capabilities, such as end-to-end governance and traceability of development/test assets.

Likewise, TFS (Team Foundation Server) also requires another component which is client-based called VSTS/Visual Studio Team Services to provide full ALM capabilities.

Usually, a choice for TFS is made when the development technology stack is based mainly on Microsoft, such as .NET. The Microsoft suite comprising .NET, TFS, and VSTS is an entire ecosystem that serves that technology stack very well. It is a licensed solution.

If the development technology stack is more diverse, e.g., includes Java, Python or other similar technologies, then a solution that includes Jira (which is open source) plus Micro Focus ALM or Zephyr (which are licensed) tends to be more popular. The integration of all the diverse technologies tends to be better with Jira.


Let me know if this helps, or requires more explanation.

14 March 18
MohammedIdaisReal User

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.

15 March 18
Sven MatzenUser

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.

14 March 18
Juan-PerazaVendor

For complete ALM, I would consider MicroFocus ALM Octane? I have worked at a shop where I used and was an administrator of JIRA. As Rene stated, it's not an ALM solution. Take a look at this Octane demo - https://www.goconsensus.com/app/view/p/q33mf86w?autoplay=false

13 March 18
Ranking
Views
64,510
Comparisons
55,853
Reviews
32
Average Words per Review
296
Avg. Rating
8.3
Views
27,590
Comparisons
23,203
Reviews
6
Average Words per Review
264
Avg. Rating
8.3
Top Comparisons
Compared 35% of the time.
Compared 18% of the time.
Compared 7% of the time.
Compared 50% of the time.
Compared 17% of the time.
Compared 5% of the time.
Also Known As
JIRA SoftwareTeam 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
REVIEWERS
Financial Services Firm16%
Software R&D Company14%
Insurance Company11%
Healthcare Company11%
VISITORS READING REVIEWS
Software R&D Company25%
Financial Services Firm11%
Manufacturing Company11%
Comms Service Provider10%
REVIEWERS
Financial Services Firm43%
Manufacturing Company13%
Software R&D Company13%
Retailer9%
VISITORS READING REVIEWS
Software R&D Company23%
Financial Services Firm12%
Manufacturing Company10%
Comms Service Provider9%
Company Size
REVIEWERS
Small Business32%
Midsize Enterprise20%
Large Enterprise49%
VISITORS READING REVIEWS
Small Business10%
Midsize Enterprise15%
Large Enterprise75%
REVIEWERS
Small Business13%
Midsize Enterprise21%
Large Enterprise66%
VISITORS READING REVIEWS
Small Business2%
Midsize Enterprise12%
Large Enterprise87%
Find out what your peers are saying about JIRA vs. TFS and other solutions. Updated: September 2019.
372,124 professionals have used our research since 2012.
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 Up with Email