Try our new research platform with insights from 80,000+ expert users

Jira vs Polarion Requirements comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Jira
Ranking in Application Requirements Management
2nd
Average Rating
8.0
Number of Reviews
266
Ranking in other categories
Application Lifecycle Management (ALM) Suites (1st), Project Management Software (4th)
Polarion Requirements
Ranking in Application Requirements Management
3rd
Average Rating
7.4
Reviews Sentiment
6.9
Number of Reviews
13
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Application Requirements Management category, the mindshare of Jira is 15.3%, down from 17.3% compared to the previous year. The mindshare of Polarion Requirements is 15.6%, up from 15.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Requirements Management
 

Featured Reviews

Saroj Ekka - PeerSpot reviewer
Offers good repository integration, sprint board and easy to set up
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. We can know the capacity and what happened with the whole sprint, but not for an individual person to see where it's falling and how it's tracking. Report and analytics capabilities are important for a product manager. That visibility is important, so we use Jira. Some of the features are there, and I use my own Excels or other data things to compensate for that.
JuanCarlos Lopez - PeerSpot reviewer
Defines, builds, tests and manages complex software systems
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

Quotes from Members

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

Pros

"The design of the interface is clean and not too busy visually."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product."
"The initial setup isn't too complicated."
"With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board."
"The integration of other open source tools with Jira is very useful. It allows us to create documents and transcriptions, making it versatile beyond software development."
"The layout, workflow, automation, and metrics are helpful in Jira."
"We can cope with processes easily without adapting the tool, but adapting the tool to processes."
"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."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"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."
"I would say there is value in how powerful, configurable, and user-friendly it is."
"A valuable feature from my side would be the comparison corporization."
"We worked with the web interface."
"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."
"Its flexibility and APIs are the most valuable."
 

Cons

"I would like to see more integration available with more tools."
"Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows."
"Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly."
"A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product."
"Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."
"The reporting needs to be improved."
"There needs to be easier integration with third-parties — personally, this is the biggest issue for me."
"We'd like to see more collaboration tools implemented within the product itself."
"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."
"The platform's review process for the documents could be better."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
"The one thing I would mention is the license policy is a little bit difficult. For different roles, you will need different license models. That seems a little bit difficult for us. Especially when you introduce such a complex system, you want to know the right way is to do licensing. It's not clear what that best way would be. The solution will be here for a long time, and I just think it could be more clear."
"One thing to consider is increased flexibility in terms of workflow configuration."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
 

Pricing and Cost Advice

"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."
"It does not cost that much."
"There is a monthly license required for this solution and it is expensive."
"I think the starter pack of three users, up to five users, is free. So you can try it out."
"The tool's pricing is reasonable."
"Almost everybody uses JIRA nowadays because it is the most cost-effective solution."
"We have an enterprise license that includes cloud service and support."
"One of my customers told me that they were receiving better pricing for a similar tool from Microsoft."
"I rate the solution's pricing a seven out of ten."
"Polarion Requirements is a little pricey."
"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."
"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."
"The product's price is high."
"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."
report
Use our free recommendation engine to learn which Application Requirements Management solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
50%
Manufacturing Company
8%
Financial Services Firm
7%
Computer Software Company
6%
Manufacturing Company
31%
Computer Software Company
13%
Healthcare Company
6%
Educational Organization
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 data may be relevant to you for identifying your needs and deciding on the approp...
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 and work logs. It is easy to implement and navigate, and it is stable and scalabl...
What is your experience regarding pricing and costs for Jira?
The product is quite expensive. It costs approximately 1.2 million rand per year. It's a fixed price, depending on the modules that you get. You have specific tools, that's what you pay for. I rate...
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-like document that functions as a work item. Its collaboration features have work...
What needs improvement with Polarion Requirements?
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 under...
 

Comparisons

 

Also Known As

Jira Software
No data available
 

Learn More

 

Overview

 

Sample Customers

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 Jira vs. Polarion Requirements and other solutions. Updated: October 2024.
816,406 professionals have used our research since 2012.