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

JIRA Portfolio vs Teamwork 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 (5th)
Teamwork
Average Rating
8.4
Reviews Sentiment
7.6
Number of Reviews
3
Ranking in other categories
Project Management Software (22nd)
 

Featured Reviews

Neeraj Chaudhari - PeerSpot reviewer
Aligns with agile frameworks for streamlined project management
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 box, it would be helpful. Making the report creation process faster and easier with drag-and-drop features would be beneficial.
Ryan Beckstead - PeerSpot reviewer
A project management tool that helps to manage milestones and dependencies
We use the product to design online courses. It also helps us with media production and marketing.  Teamwork has made process management easier and much better. It is very robust and improves by making a lot of changes. It is easy to use and has lots of reports. The product is expensive. It needs…

Quotes from Members

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

Pros

"Version management is the most valuable feature of JIRA Portfolio."
"The solution is very stable."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"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."
"We have found the solution to be stable."
"The initial setup is simple."
"With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things."
"Managing product development and managing inter-team communications are also valuable features."
"The setup was very easy. Deployment was very fast for us. We started using it within two weeks."
"It is a very stable solution...The initial setup of Teamwork is easy."
"Teamwork has made process management easier and much better. It is very robust and improves by making a lot of changes. It is easy to use and has lots of reports."
 

Cons

"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. 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."
"We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version."
"Another thing could be to have an easy way to manage the Portfolio and have more ways to share and to show graphics and reports"
"The solution's look and feel could be a bit more intuitive and user friendly."
"The solution is sometimes complex to use"
"Our major team does not control or manage JIRA server well since sometimes there is trouble using the solution, which is a problem. The solution's speed needs to be improved."
"User experience should be more intuitive."
"When using a scrum board, it only shows the current or open sprint. However, we also need to see past and future sprints, which is important for planning the next sprint. To solve this, we tried using a Kanban board instead, but since we follow the Scrum methodology, it's not the ideal solution."
"The screen sharing provided by the solution can be a challenge to a user. Screen sharing is an area that needs improvement in the solution."
"The product could be improved with more integrations and a mobile app."
"The product is expensive. It needs to have a more robust and customizable calendar."
 

Pricing and Cost Advice

"We pay our fees annually, although monthly payments are also available."
"The product is really not very expensive."
"I rate JIRA Portfolio a five out of ten for its pricing."
"The pricing continues to get higher."
"The pricing of the solution is expensive."
"We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight."
"There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost."
"My company makes annual payments towards the licensing costs of the solution."
"We negotiate on pricing since we are a long-term user."
report
Use our free recommendation engine to learn which Project Management Software solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
15%
Manufacturing Company
14%
Insurance Company
6%
Educational Organization
18%
Computer Software Company
14%
Financial Services Firm
12%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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 Teamwork Projects?
Teamwork has made process management easier and much better. It is very robust and improves by making a lot of changes. It is easy to use and has lots of reports.
What needs improvement with Teamwork Projects?
The product is expensive. It needs to have a more robust and customizable calendar.
What is your primary use case for Teamwork Projects?
We use the product to design online courses. It also helps us with media production and marketing.
 

Also Known As

Portfolio for JIRA
No data available
 

Overview

 

Sample Customers

Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
PayPal, eBay, Disney, Forbes, Microsoft studios, Spotify Vevo, Lenovo, HP, Honda
Find out what your peers are saying about JIRA Portfolio vs. Teamwork and other solutions. Updated: June 2025.
860,592 professionals have used our research since 2012.