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

"We have found the solution to be stable."
"Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated."
"The tool helps us achieve more within the stipulated timeline and budget."
"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."
"I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely."
"The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs."
"Has many functionalities including good supervision and workflows."
"It is a good scalable solution that I have used for small projects and reasonably large projects."
"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."
"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."
"It has helped improve governance, mostly. People want to know where their money's going. Projects sponsors need to know what we're spending money on and what our burn rate is. Planview can give that to you straightaway."
"The sheer amount of information available in one single interface is valuable. Everything is there. It is also a lot of work to maintain all the information, but generally, you can find everything you need within this one tool."
"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."
"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."
"The most valuable features are the control and visibility that you have for portfolio management in terms of projects and capacity planning for resources along with strategies and outcomes, etc. It's so easy to access information for sharing analytics and reporting."
"The most valuable feature of this solution is the completeness of the standard, underlying metamodel."
 

Cons

"There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio."
"Currently lacks AWS integration."
"The integration needs to be done with different tools."
"We had to use assistance for the initial setup."
"It would be nice if it could provide an end-to-end solution for a project."
"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."
"I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear."
"If you want to generate a report for individual usage, it's difficult."
"I would like to be able to copy and paste from Excel into work and assignments along with roles and hours, as opposed to having to type it out one by one."
"Its support to legacy paying customers is something PlanView is not handling well.​ We were unable to implement due to lack of professional support by PlanView. ​"
"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."
"One big issue we have been having during our annual planning is that only the creator of a portfolio can edit it. This means that only the creator of a portfolio can edit which projects are included or excluded in it."
"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."
"Support is still a challenge. We find it challenging more due to the responsiveness and getting a case or ticket assigned to an analyst. That's what I was just doing. I was following up on an email that we opened last week. We haven't heard anything, so following up on that."
"The solution is stable. However, it's so robust, there's so much data, that it has the tendency to lag."
"Being the IT development manager who implements the upgrades for Planview, I would love to see more thorough testing of expenditures and more thorough testing in general. When we do an upgrade, we have to do quite a bit of testing because we can affect the bottom line."
 

Pricing and Cost Advice

"The pricing of the solution is expensive."
"Portfolio is very expensive, costing on average $2000-3000 per user per month."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six."
"The product is really not very expensive."
"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."
"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."
"This solution has a comparable pricing in comparison to other similar products on the market."
"I don't know about the actual pricing. I have not come across any costs in addition to the standard licensing fees."
"The licensing part is a bit costly in comparison with the other available PPM tools."
"Our licensing costs are probably $150,000 to $180,000 a year with 270 licenses total."
"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."
"Our licensing costs are about a quarter of a million dollars per year."
"We are on the Flex licenses."
"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.
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.