We performed a comparison between Jira and Polarion Requirements based on real PeerSpot user reviews.
Find out in this report how the two Application Requirements Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"The features that we find most valuable are the Workflow, Scrum workflow, and Dashboards."
"I have found Jira to be stable."
"Jira has a good reporting system. It also has an API, so we can do all sorts of reporting."
"I've never had a bug or a bug message that I needed to open a ticket for."
"The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks."
"It's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable."
"We can integrate a lot of tools with the solution."
"We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"Its flexibility and APIs are the most valuable."
"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."
"A valuable feature from my side would be the comparison corporization."
"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."
"I would say there is value in how powerful, configurable, and user-friendly it is."
"We worked with the web interface."
"Jira required a significant amount of system resources, particularly for larger organizations with extensive workflows and numerous projects."
"Improvements in Jira for the next release could include adding AI tools for dashboarding, making it easier to report insights, and enhancing business intelligence capabilities. It should also improve on-prem support. As far as I know, Jira's on-premise support is being discontinued. From last year onward, they stopped providing on-premise licenses and now only offer cloud support. This shift happened gradually, and I believe they now only offer cloud licenses."
"Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see."
"The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me."
"In Jira, sometimes developers are not getting alerts when Jira is moving out of the SLA to the product development team."
"I would like to have a future-proof idea of the cost and the roadmap for my class."
"One major issue that I, and even our business stakeholders, have noticed is related to Epic Link. When Epic Link's background color is a dark color, it effectively becomes unreadable. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view."
"Its UI can be improved a little bit. I know this a business tool and not a commercial tool, but it could be a little bit more interactive like the HP ALM/Quality Center, which provides you the results of graphs and gives you a lot of visual representations. I feel Jira lacks a little bit in this aspect."
"The usability of the solution should also be improved."
"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."
"One thing to consider is increased flexibility in terms of workflow configuration."
"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."
"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."
"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."
"The platform's review process for the documents could be better."
Jira is ranked 2nd in Application Requirements Management with 265 reviews while Polarion Requirements is ranked 3rd in Application Requirements Management with 13 reviews. Jira is rated 8.2, while Polarion Requirements is rated 7.4. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". On the other hand, the top reviewer of Polarion Requirements writes "Defines, builds, tests and manages complex software systems". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas Polarion Requirements is most compared with IBM Rational DOORS, Jama Connect, IBM Rational DOORS Next Generation and Helix ALM. See our Jira vs. Polarion Requirements report.
See our list of best Application Requirements Management vendors.
We monitor all Application Requirements Management 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.
