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 most valuable feature of this solution is the source linking on the commit level to git."
"The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution."
"Powerful features including a good reporting capability."
"There are a lot of different plugins for Jira. Unfortunately, we did not test so many and the big pain point for us is the rigorous handling and the roadmap of Jira. We have a portfolio and structure plugin and we have our story map plugin in Jira"
"The user interface is simple."
"Reports, analytics, and a ton of widgets, they are great and intuitive. Perfect for an agile team."
"Transparency of development projects, as well as approval processes for some business projects, has improved massively."
"The burndown chart is also helpful when it comes to reporting and allows us to know where we are going, especially during development."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"It is easier to produce documents using the platform."
"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."
"We worked with the web interface."
"A valuable feature from my side would be the comparison corporization."
"The solution is especially great for organizing folders effectively."
"Its flexibility and APIs are the most valuable."
"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 hierarchy for Jira tickets is too flat."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"It is not intuitive."
"I'd like the solution to be more secure."
"The reporting needs to be better."
"Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure."
"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."
"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."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
"It is not a stable solution, as we had issues with shared licenses."
"The platform's review process for the documents could be better."
"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."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
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.