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 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 most valuable feature of JIRA Portfolio is the visuals it provides rather than Kanban boarded tickets."
"I think the solution's most important and valuable feature is its ability to track the issues."
"The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs."
"JIRA Portfolio has many wonderful features."
"It is a good scalable solution that I have used for small projects and reasonably large projects."
"The workflow and bucket features are most helpful."
"Has good analysis integration capabilities."
"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 Kanban board has really helped us be more agile and we can keep track of everything that is ongoing."
"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."
"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."
"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."
"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."
"I like that the data that we store is available for everybody. We're not trying to hide anything. Being an administrator, I know a lot about the tool. It is very easy to show somebody how to use the tool and get used to it. Hopefully that user doesn't come back and ask the same question twice is really what it is about. It's a very intuitive product as well. For what we use the tool for today, it's easy to learn and pick up."
"The most valuable features are scheduling, resource management, and, from a project perspective, the functions like issues that change orders. They are valuable because, from a project management perspective, we use the workflows that we build for project management and do active risk management and issue management for the projects that we want for our agencies."
 

Cons

"The initial setup could use improvement."
"The reporting and dashboard capabilities have room for improvement."
"The product could do with more flexible reporting."
"The data query language needs improvement."
"It's got kind of a steep learning curve."
"Converting a task into an epic is very troublesome."
"The solution is sometimes complex to use"
"JIRA and Confluence must be linked automatically."
"The solution out-of-the-box that we established was insufficient. We had to purchase and set up OData. I don't believe that it's a great solution out-of-the-box but eventually you can get there."
"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."
"I would like a bit more flexibility, as far as the configuration, and have additional capabilities to configure, making it more flexible for our use."
"Configuring the UI in the content management system is too elaborate and too time-consuming."
"Our challenge will be this tool is complex. It is not necessarily easy to start and learn from the beginning. How do you get people who are not professionals to adopt it, use it, and not be mean about it?"
"There can be improvement on the sense of urgency because a lot of times we've exhausted everything that we can, and now, we're reaching out. So, it isn't a, "Well, have you tried to reboot this?" We've already done everything. Once we put in a ticket, there should be more of a sense of urgency on it."
"The out-of-the-box reports, as far as I can tell, are weak. We've had to build a lot of reports using Power BI, which we connected to it."
"The scheduling's kind of clunky in terms of its ability for us to see what stage work is at. They could have done better with that. It can be difficult to use."
 

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."
"The price is reasonable"
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight."
"Portfolio is very expensive, costing on average $2000-3000 per user per month."
"I do not believe that the product provides value for money since I feel that it is quite expensive."
"There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six."
"I don't think we have necessarily purchased everything that I would have liked to have seen."
"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."
"I don't know about the actual pricing. I have not come across any costs in addition to the standard licensing fees."
"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."
"Our licensing costs are about a quarter of a million dollars per year."
"We have several hundred licenses. It costs us several hundred thousand dollars a year."
"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 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."
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.