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.2%, down 1.9% compared to last year.
Planview Portfolios, on the other hand, focuses on Project Portfolio Management, holds 7.4% mindshare, up 6.6% 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 solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work."
"We use Jira Portfolio in our organization for issue tracking and task management. We had many projects. We didn't use it much for forecasting, but we did use it a bit for release planning by assigning tasks to releases. We didn't use it for project management or scenario planning; we just used it for tasks."
"The solution helps you organize projects"
"Jira's Structure, agile, and Kanban boards are helpful. I also like JQuery, which allows you to fetch the relevant set of data. We use JQuery, JQL, and the Structure board a lot. Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"The status update function is the most valuable feature."
"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."
"The most valuable feature of this solution is the completeness of the standard, underlying metamodel."
"We provided whatever feedback we had to the Planview team, and they went in and built those additional features that we requested. For example, they created a great way for our users to search for a specific resource, project, program, or role. We were not using some of the features, and we wanted them to not be visible, and they helped us with that. They also brought a feature to provide visibility into when a resource was never assigned to any task. There was no visibility to this before. This feature was really very good for visibility into the resource portfolio."
"Planview Management integrates seamlessly with other tools and systems used within the organization, such as enterprise resource planning (ERP) software, customer relationship management (CRM) systems, and collaboration platforms."
"We've brought our portfolio altogether. We have had multiple ways of reporting out what our portfolio is, whether it's in Excel, Word, or in different places. We brought all of our projects together in one place. That has worked out well for us. We've been able to manage the work on Gantt charts and our resources better. The big thing for us on research and development is around managing people's time, on which projects they are working on, and how much effort does it take to launch our projects."
"Its ability to create summary reports across multiple projects is one of the best features. They have very good data warehousing. You can put that out. You can tell that data warehousing from Planview Enterprise One is excellent."
"The data is the most valuable because the reporting that we provide out of Planview is priceless when compared to any other tool. The reporting has a variety of reports. It has the capabilities of Power BI. It gives us all these dashboards that we can show to our executive leadership, and they have been very well-received."
"We have a fairly good picture of time tracking."
"It gives us flexibility in configuring assignments. We can do both Agile Teams and non-Agile Teams. This flexibility affects our ability to meet our company's particular needs by allowing us to work in a hybrid model, some Agile Teams, and some non-Agile Teams."
 

Cons

"Currently lacks AWS integration."
"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 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."
"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 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."
"Converting a task into an epic is very troublesome."
"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."
"JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools."
"I think that the user interface needs some getting used to. It's not immediately intuitive. That's potentially room for improvement. I think also that an organization needs to have good support from some senior management to get something like Planview established."
"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."
"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."
"Some of the out-of-the-box reporting is not immediately useful and although it can be configured or customized, there are still improvements that can be made."
"There's still a lot of reluctance within the organization. We're not using all of the capabilities that we have today. We're still doing our strategic and capital investment planning on spreadsheets rather than using the capabilities that exist within Enterprise One. I definitely need to leverage the experts here at Planview to help drive a culture change. There's just a lot of reluctance on behalf of people within the company to put data into the tool."
"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. ​"
"The only area that I can see currently needing improvement is just the modernization of the look and feel of it."
"The biggest room for improvement are the scripted dialogues. The scripted dialogues are a logic that you set up to force a certain workflow or process to happen. It's very old in respect that there are no clauses that you can apply to that logic. That definitely can use a lot of room for improvement."
 

Pricing and Cost Advice

"We pay our fees annually, although monthly payments are also available."
"There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost."
"I rate JIRA Portfolio a five out of ten for its pricing."
"The product is really not very expensive."
"Portfolio is well-priced - a license for ten users costs $100 or $150 a month."
"The price could be improved."
"I use the free version for personal use."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six."
"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."
"The licensing part is a bit costly in comparison with the other available PPM tools."
"We have unlimited licenses for all of our functionalities. Since we went global, we went with that model."
"We have portfolio managers, resource managers, project managers, and time reporting licenses. These are the licenses that we have."
"In the time that I've used it, we've doubled up the amount of dollars on our intended projects."
"Our licensing fees are approximately $50,000 USD annually."
"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."
"I don't think we have necessarily purchased everything that I would have liked to have seen."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
17%
Manufacturing Company
12%
Government
8%
Financial Services Firm
16%
Manufacturing Company
15%
Computer Software Company
13%
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: March 2025.
845,406 professionals have used our research since 2012.