We performed a comparison between Jira and JIRA Portfolio based on real PeerSpot user reviews.
Find out in this report how the two Project Management Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It's easy to deploy."
"In general, the GUI is nice."
"The user interface is simple."
"Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports."
"It gave us control over all test artifacts in one place, along with easy traceability, mapping between stories, bugs, test cases, and test cycles."
"The most valuable feature is the Burndown Chart to see work that is outstanding."
"The initial setup was pretty straightforward."
"I feel the strongest feature of Jira is its workflow engine. It helps us automate our workflows within our organization. It's the one characteristic of Jira which I think can help any organization, be it in any domain."
"The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone."
"The solution has good reporting and is very user-friendly."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"The way to manage cards as a KANBAN, is really easy but when you need to track hundreds of projects, you need to be very clear in which way the things must be completed."
"The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it."
"Jira's Structure, agile, and Kanban boards are helpful. I also like JQuery, which allows you to fetch the relevant set of data. We use JQuery, JQL, and the Structure board a lot. Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts."
"Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"It should be connected to ServiceNow."
"It's also difficult to migrate through, things don't always tie-up. It's not easy to use."
"Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects."
"The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me."
"Scripts should be more readily available for implementing projects."
"From the project management perspective, I would say there are a lot of different issues that could be tweaked. There can be small improvements with traceability, for example."
"The GUI should have much better features like more graphical illustrations. There are some cases or benchmarks that we are trying to capture into a dashboard GUI's graphical summary, but unfortunately JIRA is not able to do that."
"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."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
"The product could do with more flexible reporting."
"The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA."
"The solution's look and feel could be a bit more intuitive and user friendly."
"There is room for improvement in terms of scalability."
"When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream."
"The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client."
"The reporting and dashboard capabilities have room for improvement."
Jira is ranked 5th in Project Management Software with 262 reviews while JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 47 reviews. Jira is rated 8.2, while JIRA Portfolio is rated 8.2. 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 JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Microsoft Azure DevOps. See our JIRA Portfolio vs. Jira report.
See our list of best Project Management Software vendors.
We monitor all Project Management Software 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.
