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
267
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
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
Apr 10, 2024
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
Aug 25, 2023
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

"Workflow administration is an easy process, especially with respect to defects."
"The task management aspect of Jira is pretty pure. They have a lot of great plugins that really expand your options."
"The solution has been very stable overall."
"It improved communication, as it was a popular tool, and most people enjoyed using it."
"You can record your unit testing, regression testing, UATs, et cetera."
"Jira improved our team collaboration by providing visual visibility and transparency. Everyone could see what tasks were being worked on and the progress made. The development team updated task statuses, making tracking progress and planning sprints easy. If there were any impediments or challenges, we addressed them. This process helped us track our progress."
"It has enabled us to keep track of features or projects. Previously, we used to manually keep track in Office. We now have a centralized repository for all the information."
"The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations."
"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 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."
"I like the way this solution is structured."
"We worked with the web interface."
"We can easily customize it because of the web services and open APIs. Also, the APIs are available. We integrated Polarion with one of Siemens' products, Teamcenter, which is especially useful for automotive industries. There is an open API for integration with Jira as well, so for me, customization is a strong point."
"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."
"It is easier to produce documents using the platform."
 

Cons

"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."
"In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful."
"I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports."
"Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas."
"Jira could be easier to use, especially for administrative tasks. It's quite complex, so it's important to understand it well. While the reporting and dashboards are good, there's room for improvement in some areas where extra features would be helpful."
"Tracking is important but the built-in features don't meet our needs."
"The features are not intuitive. It would be good if there were templates."
"It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins."
"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."
"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."
"One thing to consider is increased flexibility in terms of workflow configuration."
"The platform's review process for the documents could be better."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
"The risk assessment functionality needs improvement, like FMEA risk management."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
 

Pricing and Cost Advice

"When you get larger, the pricing becomes very, very steep."
"There are other solutions that are free making this solution seem expensive in comparison."
"Jira and its solution off the shelf are cheap. It is cheap for startups."
"The ballpark figure is about $100 a month."
"We currently have ten users, and it is free for ten users."
"I understand JIRA is quite expensive."
"Licensing is on a monthly basis, and it is based on what you use."
"It is an affordable tool."
"Polarion Requirements is a little pricey."
"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."
"I rate the solution's pricing a seven out of ten."
"The product's price is high."
"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."
"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."
report
Use our free recommendation engine to learn which Application Requirements Management solutions are best for your needs.
814,649 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
30%
Computer Software Company
14%
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.
814,649 professionals have used our research since 2012.