We performed a comparison between Jira and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Project Portfolio Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of Jira for sprint planning is the timeline feature, which allows for better visualization and planning of releases."
"The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
"Jira is a pretty capable product, and a lot of features are valuable. We value being able to set up separate projects and configure teams in them, set up sprints, and manage our sprints with its history tracking. These are all very useful features. It has been a very popular product for our work."
"It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want."
"Jira has a good reporting system. It also has an API, so we can do all sorts of reporting."
"This is a user friendly solution."
"I'm working in the IT department, and the ticketing system is the most important service for us. We are also using some automation add-ons. It a very good product for handling tickets and tasks and managing processes. It is also very useful and easy to use."
"In Jira, the integrations I have used so far are the repository integration, like when it gets added, or the integration with Confluence, which is good."
"Our reporting is much better. There is much more visibility on projects, schedules, tasks, and in our milestones. Now, we have a consistent way of reporting out to the committees and getting all of our schedules and milestones."
"We're still in an early stage. Things will change as we use it more. I did program reports that are important and that will provide us with value."
"I like that it's an enterprise environment. I can look across everything that's going on and have a sense of what is going on within the organization."
"The solution’s integrated product portfolio has transformed our organization’s delivery because people are a lot more accountable. When you have no accountability, then people don't always deliver the way that you want them to. Once you get accountability, they know that somebody is watching and the way that they manage their work changes quite a bit."
"The Kanban board has really helped us be more agile and we can keep track of everything that is ongoing."
"I would say it works really well for forecasting remaining effort, especially in terms of forecasting the dollar amounts. We've gotten pretty good at adjusting rates because we have a lot of contract workers."
"We provided whatever feedback we had to the Planview team, and they went in and built those additional features that we requested. For example, they created a great way for our users to search for a specific resource, project, program, or role. We were not using some of the features, and we wanted them to not be visible, and they helped us with that. They also brought a feature to provide visibility into when a resource was never assigned to any task. There was no visibility to this before. This feature was really very good for visibility into the resource portfolio."
"We use expenditures quite a bit. We put in forecast expenditures and then we actualize them below the line in the little box in the bottom tray. Being able to track the project with relevant milestones is also valuable. Milestones are valuable because it helps us to keep the project on track. The expenditures are valuable because we need to be able to understand expenses that are beyond the regular resources in the projects."
"When you first start to use the interface, it is confusing."
"The performance could be improved in the future."
"The hierarchy for Jira tickets is too flat."
"Its search and reporting can be improved. They are already nice, but they can be further improved."
"I don't know if it's the way it's deployed in the organization, but the interface we are provided is not as customizable as other tools. The multi-language report is not enabled in our installation. I don't really know if it's something related to the tool or our installation."
"If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool."
"I do know the initial setup was pretty complicated. The user interface could be better organized and easier. "
"Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper."
"We do have some significant issues with our integrations that we're working through. Those are not as stable or reliable as what we would like."
"When it comes to reporting there are some challenges with integration."
"We are not very happy with the customer service. This is one of our main pain points. It doesn't cover the entirety of customer service, as there are reps who are really great and we've had good experiences. Many times, we've had people give us attitude, there was a delay in the response, or just a lack of interest. This got to the point where if there was a problem, we would rather try to solve it ourselves then call customer support."
"Our version is definitely set up a bit more waterfall world. It would be better if some of the agile features were more in the standard product."
"The content management definitely needs to improve. We don't really use content management for projects inside Enterprise One. We have actually switched to a SharePoint site. We have a feed from Enterprise One every night of all the projects that are created."
"The scheduling's kind of clunky in terms of its ability for us to see what stage work is at. They could have done better with that. It can be difficult to use."
"The UI needs improvement. The UI should have more possibilities for users who are not specialized in using Planview. At the moment, it is more of a technical UI. I would like it to be an open user UI."
"The lack of templates harden the initial learning curve."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. Jira is rated 8.2, while Planview Portfolios is rated 8.0. 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 Planview Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, Planview ProjectPlace and Wrike. See our Jira vs. Planview Portfolios report.
See our list of best Project Portfolio Management vendors and best Project Management Software vendors.
We monitor all Project Portfolio 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.
