Try our new research platform with insights from 80,000+ expert users

JIRA Portfolio vs Planview Portfolios comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JIRA Portfolio
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
59
Ranking in other categories
Enterprise Agile Planning Tools (5th)
Planview Portfolios
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
63
Ranking in other categories
Enterprise Architecture Management (11th), Project Portfolio Management (7th)
 

Mindshare comparison

While both are Application Lifecycle Management solutions, they serve different purposes. JIRA Portfolio is designed for Enterprise Agile Planning Tools and holds a mindshare of 1.2%, up 1.1% compared to last year.
Planview Portfolios, on the other hand, focuses on Project Portfolio Management, holds 6.3% mindshare, up 5.9% since last year.
Enterprise Agile Planning Tools Market Share Distribution
ProductMarket Share (%)
JIRA Portfolio1.2%
Microsoft Azure DevOps37.9%
GitLab30.6%
Other30.299999999999997%
Enterprise Agile Planning Tools
Project Portfolio Management Market Share Distribution
ProductMarket Share (%)
Planview Portfolios6.3%
ServiceNow Strategic Portfolio Management8.3%
Planisware8.1%
Other77.3%
Project Portfolio Management
 

Featured Reviews

Neeraj Chaudhari - PeerSpot reviewer
Delivery Leader : Digital Productivity Studio at a energy/utilities company with 10,001+ employees
Aligns with agile frameworks for streamlined project management
User experience should be more intuitive. Currently, it's not that intuitive. Additionally, a lot of querying and customization is needed for reporting. If there could be some templates out of the box, it would be helpful. Making the report creation process faster and easier with drag-and-drop features would be beneficial.
RB
PM Systems Analyst at a insurance company with 5,001-10,000 employees
Increases our on-time completion rate and helps in managing the demand and capacity, and we get excellent service in terms of feature requests and support
We've been encouraging our users to manage their schedules directly in the Work and Assignments module. So far, it has been good, but we've been in conversation with the vendor product team to improve the performance of the Work and Assignments module. Right now, it is a bit slower. We don't use the Progression feature. We will use it at some point in time. Until then, we want to have a way to set time to help decide what's in the past, present, and future. It is one of the things we've been discussing with Planview. It provides flexibility for configuring assignments, but one of the things about which we've been talking to Planview is related to certain resources that are associated with a project. When the project extends, their demand also equally goes up. There are also resources where if a particular task has to crash, it may need additional effort. So, it is between the fixed effort versus fixed duration. Planview is more duration-based. For example, if you crash a task, the system rightly thinks that you're crashing the task, and you need to finish the work by doing overtime or working additional hours. If you are taking 30 hours to finish a task in three weeks, and for whatever reason, you have to crash the task into two weeks, 30 hours need to be fulfilled within those two weeks. If the task moves to four weeks, instead of three weeks, you still have 30 hours that get distributed among four weeks, so you will be able to finish the task. That makes sense for those resources that are associated with the task, but there are certain resources, such as a project manager or project administrator, for whom when a project extends, the demand also equally goes up. So, if somebody is assigned 50% for a project, and assuming that the project is moving out by a month or two or three months, the effort shouldn't go down. Currently, the allocation goes down, and our resource managers have to go and update the effort back up to 50% or whatever the demand is. We are interacting with Planview to provide a solution. Right now, we have to go and update the additional demand because of the change in the project.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"What I like about the product is its extensive features, particularly the wide set of attributes for tracking issues. Jira Portfolio allows us to track not only the overall project but also specific components within it. This is beneficial for all stakeholders, including developers and business owners. For example, business stakeholders can track all issues, regardless of status."
"The most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin."
"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."
"I think the solution's most important and valuable feature is its ability to track the issues."
"The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability."
"We have found the solution to be stable."
"Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company."
"JIRA has helped us reduce the rate of unseen or undetectable issues in the future. It has also helped us understand the demand overload across the defense team, including capacity and availability, and how we can leverage different teams to ensure overall success."
"Whenever we have issues, there is always someone ready to help us. Their people are knowledgeable and responsive. They get to tickets quickly. Just three or four weeks ago, we were having issues with getting data into Planview. We submitted a ticket and the turnaround was probably 45 minutes to get a response."
"When it comes to managing project plans, Enterprise One is awesome at enabling us to see what stage work is at. I've always thought it was awesome because it's good whether we're doing a traditional WBS or we're linking in epics into projects that are supporting the programs and the strategies, I've always thought it was an excellent tool."
"The most valuable feature of this solution is the completeness of the standard, underlying metamodel."
"Another good thing is that we can create custom reports, which is great. If I created a custom report, a tile that tells me how many people have logged in today. We currently have a little under 2000 users, and that's only users, we actually have integrations, that we created a custom form that sends hours directly to Planview. They're not using Planview directly, but they're sending their hours to Planview through an API."
"Enterprise One has enabled us to eliminate Excel. We don't track financials anymore in an Excel format, which the company was doing before. Even now, being a new portfolio manager four months in, I'm able to just pick up my project. I'm able to see where I am right now. That improvised it to be more automated. The only missing part is the integration between tools. I'm not able to see my full schedule, but I know what are my important milestones are like watching the financials and all that stuff."
"In my opinion, the financial planning feature is the most valuable feature of Planview Enterprise One."
"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."
"It has been effective for our delivery. It's given us much better visibility into what is being delivered and when."
 

Cons

"The solution's look and feel could be a bit more intuitive and user friendly."
"Requires some effort to insert functionalities and that could be simplified."
"The initial setup could use improvement."
"The integration needs to be done with different tools."
"The solution’s pricing could be reduced."
"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."
"In the next release, Portfolio should include more metrics and develop their portfolio planning."
"I think the solution can improve in graphs and the analysis part."
"We have almost like a third-party group who has to do a lot of our configurations. It's a bit painful for us anytime we want to make a change. The other issue is that we have different groups all in the same instance. So, if one group wants to make a change, it impacts everyone. Then, we all have to come together, to say, "Yes, we approve this change, or no, we do not." Thus, it has not been as flexible for us."
"The lack of templates harden the initial learning curve."
"When I started working with Planview, I didn't know anything about project or resource management. I had to learn everything: the admin side, then the user side of it. Probably, in the beginning, I would implement in the blueprint or workshops more demos. A live demo of how the system works because we would like a little deeper dive in how the application works for us to understand what we need to provide, what we are doing, what we will be doing. Because in the beginning, it was so overwhelming, and we didn't know anything about the tool."
"The financial piece of the tool could be better. While it may have to do with the complexity of the work that we do, it seems that the tool should be able to drill down a bit deeper into the financial area."
"The only area that I can see currently needing improvement is just the modernization of the look and feel of it."
"The solution is stable. However, it's so robust, there's so much data, that it has the tendency to lag."
"It is not an end-user-friendly product, and that's really the biggest thing. The hardest or the biggest hurdle I've ever had to face was adoption. I did the installation of the HP product in 2011. The company used it from 2011 to 2015, and the adoption was very high. When I was given the Planview product, adoption was very low. It wasn't as extensively used. We actually had people who wanted to go back to HP PPM because the interface of Planview was so broken, and it still is to some degree. So, it is not user-friendly. It doesn't flow the way a project manager thinks. What we did with HP PPM was a lot more manual programming. It wasn't as nice in terms of the interface, and it wasn't as pretty, but you could design it and build it so that everything flows with the way you worked, but Planview doesn't quite do that. There are a lot of screens. You have to jump back and forth. There are so many different places you have to go to just to do some basic tasks. That's the biggest thing that has really hindered adoption."
"There are some issues with how long it takes to load the data to Planview, It just depends on what your setup is. If there was a way Planview could maybe make the loading faster, in case you do have a lot of things going on with your setup."
 

Pricing and Cost Advice

"The solution is offered at a high cost"
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight."
"The pricing of the solution is expensive."
"Given the solution’s significant functionality, benefits, and value, you get more than you pay for."
"The product is really not very expensive."
"I use the free version for personal use."
"We have a license to use JIRA Portfolio, we are not using the free version."
"The price is reasonable"
"Our licensing costs are about a quarter of a million dollars per year."
"The cost of other pieces and integrating them in needs improvement."
"The licensing part is a bit costly in comparison with the other available PPM tools."
"We are on the Flex licenses."
"Planview is a little pricey. From a licensing perspective, for just a simple timesheet user who does nothing in the system but reports time, the licensing is a little pricey, but you have to look at it from what it is that you get. We have 6,000 users, and I don't manage the system at all. I just have to do add them to the system. The servers, maintenance, OS levels, security patching for the OS, and all other things are not something that we maintain. So, you have to look at it from an operational perspective. It is not just the product itself. A holistic view has to be taken when you look at the product and how you're going to support it. I would have to hire an entire operation staff to bring it in-house, and at the end of the day, that might cost me more."
"Our licensing costs are probably $150,000 to $180,000 a year with 270 licenses total."
"In the time that I've used it, we've doubled up the amount of dollars on our intended projects."
"With the costs, they were very understanding. Knowing that we were an existing customer, they were very much willing to work with us to make sure that we were able to transition to Enterprise One from PPM Pro."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
879,310 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
16%
Financial Services Firm
11%
Computer Software Company
11%
Transportation Company
7%
Manufacturing Company
14%
Computer Software Company
10%
Financial Services Firm
8%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise12
Large Enterprise32
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise58
 

Questions from the Community

What do you like most about JIRA Portfolio?
The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
What is your experience regarding pricing and costs for JIRA Portfolio?
I am part of the delivery team and am not exposed to the commercial information. However, from what I understand, JIRA is competitively priced. It is not considered expensive in the market.
What needs improvement with JIRA Portfolio?
The setup process for JIRA Portfolio is complex.
What do you like most about Planview Portfolios?
Planview Management integrates seamlessly with other tools and systems used within the organization, such as enterprise resource planning (ERP) software, customer relationship management (CRM) syst...
What needs improvement with Planview Portfolios?
Enhancements are needed in: Advanced reporting and analytics: While Planview Management provides robust reporting and analytics capabilities, further enhancements could include more advanced data v...
What is your primary use case for Planview Portfolios?
We use Planview Management to assess the current project portfolio, evaluate resource availability, and prioritize projects based on strategic objectives, ROI, and risk factors. Planview Management...
 

Also Known As

Portfolio for JIRA
Planview Enterprise One, Troux
 

Overview

 

Sample Customers

Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
UPS, NatWest, Ingram Micro, Canadian Tire, Viessmann, Volvo, NASCO, UNESCO
Find out what your peers are saying about JIRA Portfolio vs. Planview Portfolios and other solutions. Updated: December 2025.
879,310 professionals have used our research since 2012.