Try our new research platform with insights from 80,000+ expert users

Jira 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
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
278
Ranking in other categories
Application Lifecycle Management (ALM) Suites (1st), Application Requirements Management (2nd), Project Management Software (1st)
Planview Portfolios
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
63
Ranking in other categories
Enterprise Architecture Management (11th), Project Portfolio Management (7th)
 

Featured Reviews

Akhil Viswam - PeerSpot reviewer
Senior Consultant at a consultancy with 10,001+ employees
Agile workflows have streamlined sprint planning and tracking for faster feature delivery
Jira has a very good interface and it is very easy to manage sprints, tasks, and epics. The main feature is the hierarchy, as features can be converted into epics and topics, allowing bigger tasks to be partitioned into smaller ones. The hierarchy feature in Jira helps the team significantly compared to other tools that have been used, such as Trello, which is mainly useful only for a waterfall model. For modern Agile practices, Jira is the most adapted tool in the industry. Another valuable feature is that Jira APIs have been used for data science projects to analyze tasks and get insights. This has also been very helpful in the project.
it_user1684173 - PeerSpot reviewer
PM Systems Analyst at a insurance company with 5,001-10,000 employees
Increases our on-time completion rate and helps in managing the demand and capacity, and we get excellent service in terms of feature requests and support
We've been encouraging our users to manage their schedules directly in the Work and Assignments module. So far, it has been good, but we've been in conversation with the vendor product team to improve the performance of the Work and Assignments module. Right now, it is a bit slower. 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. It provides flexibility for configuring assignments, but one of the things about which we've been talking to Planview is related to certain resources that are associated with a project. When the project extends, their demand also equally goes up. There are also resources where if a particular task has to crash, it may need additional effort. So, it is between the fixed effort versus fixed duration. Planview is more duration-based. For example, if you crash a task, the system rightly thinks that you're crashing the task, and you need to finish the work by doing overtime or working additional hours. If you are taking 30 hours to finish a task in three weeks, and for whatever reason, you have to crash the task into two weeks, 30 hours need to be fulfilled within those two weeks. If the task moves to four weeks, instead of three weeks, you still have 30 hours that get distributed among four weeks, so you will be able to finish the task. That makes sense for those resources that are associated with the task, but there are certain resources, such as a project manager or project administrator, for whom when a project extends, the demand also equally goes up. So, if somebody is assigned 50% for a project, and assuming that the project is moving out by a month or two or three months, the effort shouldn't go down. Currently, the allocation goes down, and our resource managers have to go and update the effort back up to 50% or whatever the demand is. We are interacting with Planview to provide a solution. Right now, we have to go and update the additional demand because of the change in the project.

Quotes from Members

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

Pros

"The initial setup isn't too complicated."
"The scalability is good."
"I have found the most valuable features of Jira to be ticketing, life cycle workflow, definition, and creation. Many of the features are useful."
"The informatics is the most valuable feature. It captures what we need."
"We have the best community to support any problems that we have."
"The most valuable feature is managing software development."
"It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days."
"The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features."
"The portfolio and technology management are well built."
"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 flexibility on offer is very helpful in meeting the organization's needs."
"It has been effective for our delivery. It's given us much better visibility into what is being delivered and when."
"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."
"It gives us the vast ability to churn out-of-the-box reports and have an overview about approach rates and resource utilization."
"Its view into resource capacity and availability helps us to manage work. In reporting, we use this facility to help with resource capacity and availability. It also helps to see how much we are using. We derive that information from the work and resource management screen. That is very helpful."
"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."
 

Cons

"The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes."
"Jira could be more, for example, like Micro Focus, which is what I mostly work with currently."
"I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches."
"What could be improved is the migration between the testing and production environments. This could be automated somehow as the manual transfer of certain workflows and functionalities is very time consuming right now."
"The documentation on how to create dashboards and take advantage of other features in the tool are areas where the tool has certain shortcomings."
"There is always a bit of a performance problem. It's a bit slow to load the whole data."
"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 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."
"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."
"There are some issues with how long it takes to load the data to Planview, It just depends on what your setup is. If there was a way Planview could maybe make the loading faster, in case you do have a lot of things going on with your setup."
"Their off-shore support is something new that they're laying out and the team just needed some development in terms of skill and experience."
"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."
"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 solution needs to be better at accepting new ideas for upcoming releases."
 

Pricing and Cost Advice

"I think the starter pack of three users, up to five users, is free. So you can try it out."
"The cost is about $10 per user, per month."
"I don't have the number, but I sure wish Jira was less expensive. Its price point should be a little lower, and it should be more flexible for users who are just ticket viewers."
"The price of Jira is reasonable."
"Our client handles the licensing aspect. They have not yet purchased the premium version."
"As a company, we get a subsidized price, and it's lower than what's quoted on their website."
"Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost."
"Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis."
"The cost of other pieces and integrating them in needs improvement."
"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 are on the Flex licenses."
"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 costs are probably $150,000 to $180,000 a year with 270 licenses total."
"Our licensing fees are approximately $50,000 USD annually."
"When we went through that process, I believe it is competitive with others on the market. However, there are less expensive options available. It's a more premium offering at a higher price."
"Our licensing costs are about a quarter of a million dollars per year."
report
Use our free recommendation engine to learn which Project Portfolio Management solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
18%
Financial Services Firm
10%
Computer Software Company
8%
Government
7%
Manufacturing Company
15%
Financial Services Firm
8%
Marketing Services Firm
8%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business106
Midsize Enterprise56
Large Enterprise150
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise59
 

Questions from the Community

Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below data may be relevant to you for identifying your needs and deciding on the approp...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
What is your experience regarding pricing and costs for Jira?
Jira itself is fairly priced for the features it provides, but pricing is a bit higher than some alternatives, mostly because many plugins and add-ons are paid and licensed per user. So even if onl...
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 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...
What is your primary use case for Planview Portfolios?
We use Planview Management to assess the current project portfolio, evaluate resource availability, and prioritize projects based on strategic objectives, ROI, and risk factors. Planview Management...
 

Also Known As

Jira Software
Planview Enterprise One, Troux
 

Overview

 

Sample Customers

Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.
UPS, NatWest, Ingram Micro, Canadian Tire, Viessmann, Volvo, NASCO, UNESCO
Find out what your peers are saying about Jira vs. Planview Portfolios and other solutions. Updated: February 2026.
881,733 professionals have used our research since 2012.