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 UI is good. It's simple and not very complicated. It's very good for tracking."
"I have found Jira to be stable."
"With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board."
"The level of stability is quite good."
"Kanban boards are most valuable"
"We use Jira for project management and tracking."
"The sprint tracking is really helpful and very convenient."
"The most valuable feature is managing software development."
"I like that the data that we store is available for everybody. We're not trying to hide anything. Being an administrator, I know a lot about the tool. It is very easy to show somebody how to use the tool and get used to it. Hopefully that user doesn't come back and ask the same question twice is really what it is about. It's a very intuitive product as well. For what we use the tool for today, it's easy to learn and pick up."
"The solution is flexible. Planview is always introducing new releases and functionality, which ends up being beneficial to the company. We are able to do some customizations on our own along with our IT department, and that's very helpful."
"The most valuable features are scheduling, resource management, and, from a project perspective, the functions like issues that change orders. They are valuable because, from a project management perspective, we use the workflows that we build for project management and do active risk management and issue management for the projects that we want for our agencies."
"The most valuable features are the resource management, the time sheet entry and usage, and the financial planning. With our projects, we primarily focus on resource assignments, as far as determining the actual forecast and actuals of our projects. A lot of it is based off of the resources utilized on those projects. The time based helps us capture the actuals. The amount of time people are spending on working on their project tasks. Because they've built this into the schedule, so we can build the forecast. With financial planning, we're able to look back on what our variance is and if there is anything between the scheduled forecasted hours, dollars against the actual hours, and the costs that they utilize."
"I like that everyone is able to see the same data. All of our users who aren't just time reporters have read access to all the data that is out there. So, it is one source of truth where everybody can go in and see the exact same data that everybody else sees. It is transparent."
"Enterprise One provides a variety of types of resource assignments for assigning work to people. It's very easy and straightforward to configure these assignments. Planview allows us to see the entire workforce. We can see where our skill sets of people are, what they're working on, and allows us to make informed business decisions based on priority."
"The integration stuff from tool to tool, like Projectplace to Planview, to manage projects is the most valuable feature. It keeps all our tasks up-to-date. It closely follows up with everything, which is really cool."
"The portfolio management gives you a view of all the projects as well as all the information about the total amount of effort, time, and cost being spent on the projects. It gives the organization how much money and effort should be spent towards projects so they can budget and do better capacity planning in the next fiscal year. It gives them visibility into their resources and if they have capacity."
"In Jira, sometimes developers are not getting alerts when Jira is moving out of the SLA to the product development team."
"The pricing is quite high."
"I would like to see more integration available with more tools."
"The solution lacks integration with visualization tools like Power BI or Tableau, which would be beneficial for better insights."
"This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number."
"Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management."
"The features are not intuitive. It would be good if there were templates."
"I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA."
"The out-of-the-box reports, as far as I can tell, are weak. We've had to build a lot of reports using Power BI, which we connected to it."
"The solution needs to be better at accepting new ideas for upcoming releases."
"When we first deployed, there were some issues. We never got to the root cause of why they happened. Since we didn't have any history with it, we weren't quite sure if this was a standard operating procedure or it truly was a glitch."
"The reporting capability and access to the fields for our system administrators to have access to the data without having to pay Enterprise One to get the data that's needed to create custom reports for management to create reports need improvement."
"I would suggest for the request module that they open up the fields and columns so it's like we are doing our work in the work module. You can't do that with today. We also have to make sure that the fields can go both ways with the request and work modules. Including fields in the column sets would be helpful, because today they only use attributes."
"Its reporting needs to be improved. My main complaint when it comes to Planview is that it is good to maintain all the data but to actually use the information that is in it, you actually have to use a different tool. We use Power BI. So, we pull all the information, and then we use a Power BI dashboard to stage or look at the information."
"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."
"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."
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.
