No more typing reviews! Try our Samantha, our new voice AI agent.

IBM DOORS vs Jira vs Polarion Requirements comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Mindshare comparison

As of April 2026, in the Application Requirements Management category, the mindshare of IBM DOORS is 27.4%, down from 33.9% compared to the previous year. The mindshare of Jira is 11.2%, down from 15.8% compared to the previous year. The mindshare of Polarion Requirements is 16.9%, up from 15.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Requirements Management Mindshare Distribution
ProductMindshare (%)
IBM DOORS27.4%
Jira11.2%
Polarion Requirements16.9%
Other44.50000000000001%
Application Requirements Management
 

Featured Reviews

Amol Dumbre - PeerSpot reviewer
Software Manager at Forvia
Integrated lifecycle management has supported global A‑SPICE projects and custom reporting
I believe the toolchain currently covers all of our requirements. Even for A-SPICE and related requirements, I can add attributes and manage things effectively because the tool is highly customizable. I can continue updating things and managing different processes. The only gap I have identified is in code-level coverage reporting. I have coverage traceability from IBM DOORS through the architecture and design, but I am unable to demonstrate code-level coverage reporting. That reporting capability would be helpful. Testing is covered very well through IBM Test Manager. The traceability to code is something I feel there may be certain gaps in, though I may not be fully aware of all capabilities since my role is different and I primarily receive reports rather than being an end user. Regarding the traceability feature, I am not an end user but rather receive reports from my team, so my perspective is limited.
Akhil Viswam - PeerSpot reviewer
Senior Consultant at a consultancy with 10,001+ employees
Agile workflows have streamlined sprint planning and tracking for faster feature delivery
Jira has a very good interface and it is very easy to manage sprints, tasks, and epics. The main feature is the hierarchy, as features can be converted into epics and topics, allowing bigger tasks to be partitioned into smaller ones. The hierarchy feature in Jira helps the team significantly compared to other tools that have been used, such as Trello, which is mainly useful only for a waterfall model. For modern Agile practices, Jira is the most adapted tool in the industry. Another valuable feature is that Jira APIs have been used for data science projects to analyze tasks and get insights. This has also been very helpful in the project.
reviewer2798628 - PeerSpot reviewer
Project Manager at a manufacturing company with 51-200 employees
Comprehensive traceability has supported regulated projects but review workflows still need improvement
The ability to manage requirements through the whole project life is somewhat unclear. We are not using the ability to track all requirements through the whole project life for analytics very much. We have a way to easily find all the requirements of a complex product, even if they are spread over different Polarion Requirements projects. We do not have any issues in that area, but we are not really using the analytics part of Polarion Requirements. I am satisfied with the integration capabilities for Polarion Requirements, but it depends. We encountered a lot of issues with the integration with Enterprise Architect. We were in contact with Lemon Tree company, which provides support for that integration, but we eventually decided to develop our own plugins for Polarion Requirements. That is unfortunate, but we are not really happy with their implementation. There are things that are going really well, but alongside this, there are also things that are not yet implemented, which is quite annoying for us. The main point for improvement or lack of functions that I would like to address in Polarion Requirements is really about the review process, which is a bit too limited. When we are developing complex products, we have to review big life documents or a set of work items, but there are a lot of issues with that. For example, very simple things: if you select a word and not a space in the document, you are not able to add comments, and it is not user-friendly. If you know that you have to put the cursor and not select the word, that is something people can live with, but for newcomers, it is frustrating. They will ask questions such as 'I cannot add a comment about this word' or for a selection of text. That is something annoying. You can do that in a simple Word document, but not in Polarion Requirements. Also, the ability to review a table or generated dynamic content is not possible in Polarion Requirements. For example, if you generate automatically a list of tests, you cannot click on the second one; you can only click at the beginning of the generated sections. I am somewhat satisfied with Polarion Requirements' functionality, but I feel a lack of certain functions regarding the review, which is a bit too limited. The review process is the main pain point for me, especially since we are in a highly regulated environment where reviews are crucial for us.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It has improved our ability to do traceability back to our initial requirements."
"The program is very stable."
"It helps us to standardize the way our globally distributed teams are now collaborating and managing the different artifacts."
"Very customizable and can be as powerful as you want it to be."
"Rational DOORS' most valuable feature is that you can write any kind of requirement you want."
"We have different generations of all products. It lets us select and see unique attributes for each release or generation. You can use attributes to define a selection area to see which equipments are for the old versions and which ones are for the new versions. This inbuilt view is what I like in IBM Rational DOORS. So, for a database and a set of requirements, it will select and show unique attributes for a release or a generation."
"I really enjoyed the API."
"Traceability on requirements for a huge project in an organization is a big gain."
"The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence."
"Jira is very useful for project management for internal projects."
"It was very easy to learn Jira. As a scrum master, I run daily stand-ups, and they are run directly from Jira. The feature that I really love in Jira is called Issue Navigator. It allows me to customize how I want to show the user stories within Jira to my squad."
"We use Jira mostly for task coordination and assignment, and additionally scrum methodologies define work items and bug issues, and if we create any bugs all of them are fixed."
"I like seeing which tickets are open and what our response rate is. They have a lot of good metrics in their system to see what's going on."
"Tracking and accountability have been improved, as with the advanced workflows, one can ensure processes are followed, and it is easily seen through one of the many reporting options exactly who is doing what and when."
"Jira has a useful user interface and overall is easy to understand and learn."
"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."
"I would say there is value in how powerful, configurable, and user-friendly it is."
"My company mainly utilizes the product for documenting internal standards, guidelines, and requirements. Currently, we're focusing on using it for internal purposes, but the vision is to expand its usage to include contract requirements and tracking functionalities. While we're not there yet, it has proven effective for managing our internal documentation needs."
"The biggest improvement would be in the transparency we have now, as we have very complex products and make whole systems with difficult and diverse areas such as hardware, software, mechanical and printing, and to get the overview of all the requirements into a system at that sizing is the main advantage we have in the organization now."
"In my opinion, Polarion Requirements' most beneficial feature is the ability to manage specifications within a work-like document that functions as a work item. Its collaboration features have worked very well and have been very useful. We can easily exchange information with the testing team, the business, and with DevOps."
"The most beneficial features of Polarion Requirements for traceability include the traceability function and also the historical and matchmaking or cross-referencing, which was very good."
"The biggest improvement would be in the transparency we have now. We have very complex products. We make whole systems with difficult and diverse areas such as hardware, software, mechanical and printing, etc. To get the overview of all the requirements into a system, at that sizing, is the main advantage we have in the organization now."
"I like the way this solution is structured."
"A valuable feature from my side would be the comparison corporization."
 

Cons

"One thing that I would like to see is a lower-cost version of it that we could use for smaller projects. Sometimes, we do projects for commercial customers who would benefit from something like DOORS, but it's just so expensive. It's just a monster, so a lower-cost version would be the thing that we'd like to see."
"The strict requirements for synchronization of the data could be relaxed. It requires a permanent connection with good bandwidth."
"There needs to be quicker access to tech support. When I have a two minute question that takes two minutes to answer, it shouldn't take me 45 minutes and/or a few days of callbacks to get to the right technical support person. It's unnecessary and frustrating for the user."
"One of the things that many people complain about is it's hard to manage attributes. For example, tables or figures. This is something that can be improved."
"IBM DOORS should cover all engineering functions seamlessly, not just requirement engineering."
"The web application DOORS Web Access doesn't have the same functionality as the standard client, so it's not a real substitute."
"The customer must also have the tool to import the changes and accept them as a part of the review."
"I would rate technical support a six on a scale of one to ten. I have tried to contact them twice and never heard anything back."
"There is no one system on which TAMs and their customers can collaborate on action items, ongoing projects, meeting notes, etc."
"The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details."
"I prefer to use Azure DevOps instead of Jira for stability or the frequency of use."
"We would like to see integration between Tempo and Jira."
"I would like our clients' IT group to be able to have oversight without setting up agents. We're managing tickets, and I'd like their IT group to see everything we're doing without having to set them up as agents. There should be a better way of managing their users. I've got such requests, but Jira is expensive, and it is difficult to pay an agent fee for somebody else to view these tickets. Currently, the only way in which I can do that is by setting a user up as an agent, and it becomes cost-prohibitive. They need to do a better job on ticket viewers."
"I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"Jira can improve by making methodologies better, such as scrum and agile. Additionally, improvements in Kanban boards are needed."
"The user interface and views on different devices should be improved."
"The usability of the solution should also be improved."
"One thing to consider is increased flexibility in terms of workflow configuration."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
"I am somewhat satisfied with Polarion Requirements' functionality, but I feel a lack of certain functions regarding the review, which is a bit too limited."
"Its user interface could be more user friendly. In addition, a lot of features are missing for test management. It should have the test case ordering feature."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
"In my opinion, the main area for improvement in Polarion Requirements is its user interface. It should be easier for engineers to understand how it works, as many features are not very easily understandable for end-users."
"We encountered numerous challenges, such as issues with requirements, project management, timing, and planning. The main problem with Polarion at the outset, I believe, was our limited understanding of the planning phase. During that time, we were more focused on change management related to requirements. Recognizing the importance of planning has been a key realization for us. Another mistake we made was not comprehending the need to document these requirements to manage all the work items effectively. Now, we understand the significance of this documentation. As a result of these insights, we have started to see a growing number of competitors from Polarion in this field. One potential improvement could be enabling Polarion to export work items not just to Microsoft Office but also to other office tools."
 

Pricing and Cost Advice

"It is expensive to onboard additional users."
"The licensing cost is too high."
"IBM DOORS is available at a reasonable price"
"I don't personally know what the numbers are. I just know that one of the reasons we've limited it to three seats is a function of cost."
"I think it's expensive because you have to pay for the licenses to IBM and all that and maintain them."
"Pricing can vary depending on the size of the organization and how contracts are negotiated."
"It's expensive."
"The licensing costs for the product are quite high."
"The tool's pricing is expensive. The new pricing is indeed quite expensive compared to what it was a few years ago. Last year, when we intended to renew our subscription, we found the pricing considerably higher."
"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."
"The tool is expensive."
"There is a monthly license required for this solution and it is expensive."
"Jira and its solution off the shelf are cheap. It is cheap for startups."
"I don't feel that price is an issue."
"There is a need to make yearly payments towards the licensing costs attached to the solution. The product offers flexibility in pricing since it depends on the memory bits you have used."
"I rate the solution's pricing a seven out of ten."
"It is expensive but not for what it is. It is just the right price for what it is. Its price is also similar to other solutions."
"The product's price is high."
"I believe the cost is subjective. It seems a bit pricey, but it depends on your perspective. To provide some context, I compared the prices with GitLab and Jira. Unfortunately, I couldn't find Jira's prices. However, GitLab costs around 40 euros, and DeepLab, which I recently discovered, also falls in a similar price range. I'm not sure about DeepLab's features or interface improvements, as they might have been implementing requirements management over the past six months. In contrast, Polarion costs around 50 to 60 euros based on the 2021 prices I have. While it may seem a bit expensive, it's worth considering whether the additional investment, perhaps around 68 euros per user, is justified. It might appear costly at first glance, but it's essential to acknowledge that it can greatly streamline your work processes."
"Polarion Requirements is a little pricey."
"The pricing model is flexible. You don't have to pay for the full functionalities. And it's a one-time investment for the licenses. You purchase what you need and then can work with that."
report
Use our free recommendation engine to learn which Application Requirements Management solutions are best for your needs.
885,728 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
25%
Aerospace/Defense Firm
7%
Government
6%
Construction Company
5%
Manufacturing Company
17%
Financial Services Firm
9%
Computer Software Company
7%
Government
7%
Manufacturing Company
28%
Healthcare Company
6%
Computer Software Company
6%
Construction Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise10
Large Enterprise38
By reviewers
Company SizeCount
Small Business107
Midsize Enterprise58
Large Enterprise151
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise3
Large Enterprise5
 

Questions from the Community

What is your experience regarding pricing and costs for IBM Rational DOORS?
Over the years, the first version cost something around 5800 euros.
What needs improvement with IBM Rational DOORS?
I believe the toolchain currently covers all of our requirements. Even for A-SPICE and related requirements, I can ad...
What is your primary use case for IBM Rational DOORS?
I manage the entire application lifecycle management, which includes requirement management, architecture, and softwa...
Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below d...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products a...
What is your experience regarding pricing and costs for Jira?
Jira itself is fairly priced for the features it provides, but pricing is a bit higher than some alternatives, mostly...
What do you like most about Polarion Requirements?
In my opinion, Polarion Requirements' most beneficial feature is the ability to manage specifications within a work-l...
What is your experience regarding pricing and costs for Polarion Requirements?
I purchased Polarion Requirements directly from Siemens Benelux, but if you have any ideas to get a license at a bett...
What needs improvement with Polarion Requirements?
The ability to manage requirements through the whole project life is somewhat unclear. We are not using the ability t...
 

Also Known As

Rational DOORS
Jira Software
No data available
 

Overview

 

Sample Customers

Infosys, Chevrolet Volt
Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.
NetSuite, Ottobock, Zumtobel Group, Kªster Automotive GmbH, Sirona Dental Systems, LifeWatch, U.S. Federal Aviation Administration (FAA), PHOENIX CONTACT Electronics GmbH, Metso Corporation
Find out what your peers are saying about IBM, Atlassian, Jama and others in Application Requirements Management. Updated: March 2026.
885,728 professionals have used our research since 2012.