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."For QA, the most interesting for me are boards, backlog, and filters."
"The most valuable feature of the solution is the ease of replication of tickets."
"All departments can work with the same platform."
"The layout, workflow, automation, and metrics are helpful in Jira."
"You can record your unit testing, regression testing, UATs, et cetera."
"In general, the GUI is nice."
"I have experience with Jira's bulk tracking and issue management. We use it to add new features to our product, fix bugs, and address customer feedback."
"The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
"It is easier to produce documents using the platform."
"The solution is especially great for organizing folders effectively."
"I would say there is value in how powerful, configurable, and user-friendly it is."
"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."
"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."
"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."
"The solution should be more user-friendly and include integration with different tools."
"It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios. We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration."
"Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it."
"There needs to be a way to export a user story."
"It is a bit harder for management or the business partners. I used to search the Atlassian Community online for some troubleshooting issues and I think there were some issues that seemed to not be a big problem for other similar applications, like Microsoft Teams, that were not considered by Jira."
"The support could be improved."
"Not very intuitive for project admins."
"Could be more intuitive."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
"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."
"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."
"The usability of the solution should also be improved."
"The platform's review process for the documents could be better."
"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."
Jira is ranked 2nd in Application Requirements Management with 266 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.