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.8
Number of Reviews
58
Ranking in other categories
Enterprise Agile Planning Tools (4th)
Planview Portfolios
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
63
Ranking in other categories
Enterprise Architecture Management (14th), Project Portfolio Management (8th)
 

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.1%, down 2.3% compared to last year.
Planview Portfolios, on the other hand, focuses on Project Portfolio Management, holds 6.9% mindshare, up 6.7% since last year.
Enterprise Agile Planning Tools
Project Portfolio Management
 

Featured Reviews

Gary Craven - PeerSpot reviewer
Powerful, flexible solution with a bit of a learning curve
The weakness of the solution is that the interface is a little nonstandard, meaning it's very flexible. It's got a lot of power and gives the user the ability to combine different projects into the portfolio and move user stories between projects and link them. What I have found in a couple of organizations that I've used it with, is that the uptake tends to be a little slow because it's got a bit of a learning curve. It can dump data out to Excel and those programs, but it also has a big ecosystem of plugins and add-ons that you can get. I guess it has some strength in that regard, but if you're going to run it on-prem, you have to have people that are pretty well-versed in the program and have the time and capabilities to handle integration and make sure they're adding those modules correctly. Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. Now they are moving into these new use cases, including systems development, business projects, business processes, and redevelopment projects, but there is a problem with the nomenclature that they use, and some of the documentation is a little techy for moving it into those more business-focused use cases. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.
Mark Hillman - PeerSpot reviewer
User-friendly interface, but the reporting could be improved
The reporting is poor and requires improvement. The tiles and exception-based activities in the application are sufficient to get by. However, when it comes to producing executive reports, MI reports, or any other type of reporting, we must exit Planview and work offline. We have been working with them to improve on that, as well as using some of the Power BI capabilities that have been available for a while, but it's still more difficult than it should be. In the next release, I would like to be able to use the data in the tool to gain insight much more easily.

Quotes from Members

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

Pros

"Portfolio's most valuable features are that it's user-friendly and customer-centric."
"The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects."
"The most valuable feature of the JIRA Portfolio is the many features it provides, such as code integration, documentation, roadmap, and Eclipse. The solution is useful for product managers."
"The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area."
"Has many functionalities including good supervision and workflows."
"The stability of JIRA Portfolio is very good."
"The status update function is the most valuable feature."
"The graphics and the resolution of the work are very good."
"We use time reporting. We convert time reporting into financial costs and do contractor and capacity planning for our resources. We track our work. So, that's the module we use extensively. As a matter of fact, we have upwards of 300 open projects at this given moment. It is pretty close to 300 open activities that are working."
"The financial planning capabilities are very useful. We have integration for an SAP system, and so we load financial data from SAP into Planview for prior months. And then we use the forecasting capabilities to get a complete picture of the cost of a specific project. The financial management is very useful."
"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 overall interface is very easy to use. It puts together strategy and execution across all your investments."
"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 resource management and assignment features are valuable. The timesheet management is also valuable because that is a requirement for us. So, the ability to see timesheet forecasting and timesheet actual submission from resources has been very useful and valuable to us."
"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."
"The biggest impact has been getting all these global groups into one space so we can even have intelligent conversations about what are we trying to accomplish. Before, it was just different regions doing whatever. Now, we're all talking the same language, and that's good."
 

Cons

"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."
"JIra is very poor at reporting."
"The reporting and dashboard capabilities have room for improvement."
"I think the solution can improve in graphs and the analysis part."
"The automation in JIRA Portfolio could improve, it takes some time. We have to do some other tactics to have the same integration. Manually integrating something will take more work than if it was automated, but the automation scripting in the solution is not simple."
"The HR aspect of the solution could be improved."
"With Jira, an issue that arises is the length of time it takes to show certain data."
"There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio."
"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."
"The technical people are very competent, but there is so much turnover in the people that we talk to, and that's frustrating. They will say, "We can make this work." Suddenly, that guy has left, and we have no one. Then, we have to start all over."
"The technical support is a little overworked. At least, they have been in the past year. We need them to focus on somethings from time to time. You can tell that they're really focusing on many things. It has gotten better, but I think they could still use some relief."
"It would be great to see Planview incorporate agile interfacing/methods in it. Like CA Clarity and other leading PPM tools – Planview should enhance or develop the interfaces to ingrate with other market leading Agile tools."
"The reporting is absolutely shocking. It's not good reporting and requires improvement."
"We had issues with the data rephrasing."
"We have required more time from our resource managers to spend time in the tool. The adoption has been slower than we would have hoped. So, I would think from a rollout perspective, if Planview could help us with material which gets non-Planview users or previously light Planview users to become more heavy users of the system, then this would help us with the rollout."
"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."
 

Pricing and Cost Advice

"Given the solution’s significant functionality, benefits, and value, you get more than you pay for."
"The pricing continues to get higher."
"We have a license to use JIRA Portfolio, we are not using the free version."
"The solution is offered at a high cost"
"We pay our fees annually, although monthly payments are also available."
"Portfolio is very expensive, costing on average $2000-3000 per user per month."
"The pricing of the solution is expensive."
"We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
"We overbought our licenses. We looked at our needs three to four years down the road and tried based our contract on that. However, we were over aggressive. We use about a third of the licenses that we have. We're looking to adjust the makeup so we can start utilizing the amount of money that we are spending. Right now, we're overspending, and my organization is not seeing the value in Planview because we are paying so much for licenses that we're not using."
"We recently did a new bundle for all of Enterprise One. It includes some of the newer pieces, like Projectplace and LeanKit. It bundled our CTM in with it as well. I think the total came out to be about $900,000 a year. This is for unlimited licenses."
"We are on the Flex licenses."
"We have several hundred licenses. It costs us several hundred thousand dollars a year."
"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 fees are approximately $50,000 USD annually."
"Our licensing costs are probably $150,000 to $180,000 a year with 270 licenses total."
"We have unlimited licenses for all of our functionalities. Since we went global, we went with that model."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
837,501 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
16%
Manufacturing Company
12%
Government
7%
Manufacturing Company
16%
Financial Services Firm
16%
Computer Software Company
12%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
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 ...
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 is your experience regarding pricing and costs for Planview Portfolios?
Planview Portfolios is not too expensive. You get what you paid for.
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...
 

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: January 2025.
837,501 professionals have used our research since 2012.