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

"The graphics and the resolution of the work are very good."
"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."
"We have found the solution to be stable."
"The solution is stable and reliable."
"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 is simple to use."
"Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company."
"The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it."
"The most valuable feature of this solution is the completeness of the standard, underlying metamodel."
"The overall interface is very easy to use. It puts together strategy and execution across all your investments."
"We do a lot of big projects which are pretty expensive to structure the product development around and see the progress. Every time we start a project, we have to expense the spends for certain amounts. We need some baselines, like predictive versus actual."
"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."
"The solution view into resource capacity and availability helps us to manage work."
"The most valuable feature for me is the ease and customizability of reporting."
"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 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."
 

Cons

"If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out."
"The HR aspect of the solution could be improved."
"This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing."
"I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."
"The solution’s pricing could be reduced."
"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."
"We would love to be able to have direct contact with Atlassian. Currently, they are not working directly with West African countries. We are considering using JIRA Align, but when we contact them, they say that as we are in West Africa, they don't directly work with West Africa."
"As there are no perfect solutions and considering that I rate JIRA Portfolio's stability an eight out of ten, I feel it is an area with certain shortcomings where improvements are required."
"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 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."
"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."
"Visualization and reporting areas could use improvements by having canned reports."
"Even though Enterprise One is easy and user-friendly, it could provide better training like a demo. Providing more tutorials or sessions would really help."
"The only area that I can see currently needing improvement is just the modernization of the look and feel of it."
"The resource area needs improvement. The improvements that have been made recently in the later versions have been good improvements, but I think there are some more improvements needed there."
"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."
 

Pricing and Cost Advice

"When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard they increased a lot, so we decided to stop using it."
"The pricing of the solution is expensive."
"There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost."
"I do not believe that the product provides value for money since I feel that it is quite expensive."
"The solution is offered at a high cost"
"This solution has a comparable pricing in comparison to other similar products on the market."
"I rate JIRA Portfolio a five out of ten for its pricing."
"Portfolio is very expensive, costing on average $2000-3000 per user per month."
"I think all in we are at $33,000 a year and that includes Projectplace and Planview. We used to have the integration to JIRA, but we don't pay for that anymore."
"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."
"I don't know about the actual pricing. I have not come across any costs in addition to the standard licensing fees."
"We have portfolio managers, resource managers, project managers, and time reporting licenses. These are the licenses that we have."
"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."
"The licensing part is a bit costly in comparison with the other available PPM tools."
"Our licensing fees are approximately $50,000 USD annually."
"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.