Try our new research platform with insights from 80,000+ expert users
reviewer2404761 - PeerSpot reviewer
Software development manger at a insurance company with 51-200 employees
Real User
Offers impressive scalability and stability with an effortless setup
Pros and Cons
  • "The solution helps you organize projects"
  • "The solution is sometimes complex to use"

What is our primary use case?

JIRA Portfolio is used in our organization for scrum projects. The solution helps manage projects, plan sprints, and execute the planned sprints. The development team is the major user of JIRA Portfolio in our company. 

What needs improvement?

The solution is sometimes complex to use, especially when Confluence is used along with JIRA Portfolio. 

For how long have I used the solution?

I have been using JIRA Portfolio for nearly 15 years. 

What do I think about the stability of the solution?

The solution is stable enough. I would rate the stability a ten out of ten. 

Buyer's Guide
JIRA Portfolio
April 2025
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
863,901 professionals have used our research since 2012.

What do I think about the scalability of the solution?

The solution is highly scalable and flexible as well. Even without availing of add-ons from the vendor, the basic JIRA Portfolio is enough to make customizations according to the use cases or projects. I would rate the scalability a ten out of ten. 

How are customer service and support?

Until now, at our company, we never had the need to seek customer support because we never faced any issues, downtime, or server porting with the solution. 

How was the initial setup?

The initial setup of JIRA Portfolio is quite straightforward. I would rate the initial setup an eight out of ten. As it's a cloud version, the solution setup process is very fast; you just need to create an account and mostly provide access to team members.

In most cases, one professional is enough to deploy JIRA Portfolio. I have witnessed the solution being used by small, medium, and enterprise-level companies. The setup process majorly involves getting access to the JIRA cloud and the subscription. 

What's my experience with pricing, setup cost, and licensing?

The solution is offered at a high cost and the price further escalates depending on the number of add-ons availed. The solution is very popular and a huge number of companies are using it, so I believe the product is not unaffordable. 

What other advice do I have?

JIRA Portfolio is used to track time in our company. For reporting purposes in our organization, we use Power BI, and JIRA is integrated with Power BI for all tracking needs. 

The solution helps you organize projects and it can be complex to use, especially when Confluence is used in integration with JIRA Portfolio. How someone utilizes the flexibility of JIRA Portfolio's issues, epics and stories depends upon the individual's interpretation of the solution.

The solution is worth its price to keep you on track with projects. Whether the tool gets used in the Kanban or Scrum method depends upon the development style at Agile. JIRA Portfolio is mostly used for Scrum because there are sprints available, projects can be planned from a project management perspective, ABCs can be planned, dates can be fixed and it seems more organized than other methods. 

The solution is also used in Scrum because the management, future releases and roadmaps can be planned. There are similar project management tools. I am aware that a similar tool like JIRA Portfolio is hosted by Azure, especially for developer teams, but I would still recommend JIRA Portfolio if it seems affordable to the company or professionals. I would overall rate JIRA Portfolio a nine out of ten.  

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
Works at a tech services company with 1,001-5,000 employees
Real User
A powerful tool which is very reliable and stable
Pros and Cons
  • "The status update function is the most valuable feature."
  • "The data query language needs improvement."

What is our primary use case?

I'm a product manager, so I create entries covered for two products that are developed by the engineering team.

What is most valuable?

The status update function is the most valuable feature. 

What needs improvement?

The data query language needs improvement. 

For how long have I used the solution?

I have been using JIRA Portfolio for ten years. 

What do I think about the stability of the solution?

Jira is a highly stable solution. I would rate the stability a nine out of ten. 

What do I think about the scalability of the solution?

One thousand users are using the solution at present. 

How was the initial setup?

The initial setup is straightforward. The integration with Slack is very good. 

What other advice do I have?

Jira Portfolio is a powerful tool which is very reliable and stable. I highly recommend the solution. Overall, I would rate the solution a nine out of ten. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
Buyer's Guide
JIRA Portfolio
April 2025
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
863,901 professionals have used our research since 2012.
Dennis-Graham - PeerSpot reviewer
CTO at a tech vendor with 11-50 employees
Real User
Top 10
Provides good visibility into planned work and scheduled work
Pros and Cons
  • "The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work."
  • "The solution’s pricing could be reduced."

What is our primary use case?

We sometimes use JIRA Portfolio as an agile solution. Sometimes, we use it as a kanban solution. It was all dictated by the type of work that each team does.

What is most valuable?

The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work. As new work was identified, we could properly slot it in, schedule it, and manage it. This visibility helped us increase the confidence in delivery and launching and decreased the variance to the planned launch date.

What needs improvement?

The solution’s pricing could be reduced.

For how long have I used the solution?

I have been using JIRA Portfolio for 20 years.

What do I think about the stability of the solution?

I've used the solution both on-premises and cloud, and I've never had any performance issues.

I rate the solution ten out of ten for stability.

What do I think about the scalability of the solution?

I've never had any issues with the solution's scalability or availability.

I rate the solution’s scalability ten out of ten.

How was the initial setup?

If you do not understand the environment, the deployment will not be easy. Since I have used JIRA for quite some time and understand the Atlassian ecosystem, the initial setup of the solution was very straightforward for me.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution’s initial setup an eight out of ten.

What's my experience with pricing, setup cost, and licensing?

Given the solution’s significant functionality, benefits, and value, you get more than you pay for.

What other advice do I have?

I used the solution's Advanced Roadmaps feature instead of the regular roadmap feature. I liked it because it provided a visual that allowed my leadership and my partners to understand the roadmap, when we were getting work done, and when we were launching a feature or functionality.

I've mostly found solutions when I go to the community. I google JQL a lot, which is probably the extent of my interaction with a community knowledge base.

JIRA Portfolio helps facilitate cross-team collaboration in projects. In Jira, you can explicitly define a dependency between work, issues, and items within different projects. With Advanced Roadmaps, you can create initiatives and projects that facilitate cross-team collaboration in projects.

I would recommend JIRA Portfolio to other users because it provides good visibility. Jira gives you the tools to see what work you've planned and if there are any dependencies or risks that might be creating any issues.

The solution has adopted SAFe, which is a type of process management, workflow management, and software. The Advanced Roadmaps is the type of tool that helps support SAFe methodologies, which are an extension of agile project management.

Overall, I rate the solution ten out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
Anthony Poole - PeerSpot reviewer
Chief Technology Officer Head of engenir at Stealth Startup
Real User
Top 20
A stable solution with good version management, but configuration management could be improved
Pros and Cons
  • "Version management is the most valuable feature of JIRA Portfolio."
  • "JIRA Portfolio's configuration management could be improved."

What is our primary use case?

We use JIRA Portfolio for program management for agile team development across multiple product pipelines.

What is most valuable?

Version management is the most valuable feature of JIRA Portfolio.

What needs improvement?

JIRA Portfolio's configuration management could be improved.

For how long have I used the solution?

I have been using JIRA Portfolio for at least five years.

What do I think about the stability of the solution?

JIRA Portfolio is a cloud-based solution, and I haven't had a problem with it. I rate JIRA Portfolio ten out of ten for stability.

What do I think about the scalability of the solution?

JIRA Portfolio is a scalable solution. I rate JIRA Portfolio a seven out of ten for scalability.

How was the initial setup?

JIRA Portfolio's initial setup is not intuitive and needs to be customized. I rate the solution a five out of ten for ease of initial setup.

What's my experience with pricing, setup cost, and licensing?

I rate JIRA Portfolio a five out of ten for its pricing.

What other advice do I have?

JIRA Portfolio is deployed on the cloud in our organization. My advice to people looking into using JIRA Portfolio is that it's absolutely fine if they want to use it as a standard deployment. However, the more they want to change anything, its complexity increases quickly.

Overall, I rate JIRA Portfolio a seven out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
Team Lead at Accenture
Real User
Easy to use, low maintenance, and easy ticket creation
Pros and Cons
  • "The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it."
  • "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."

What is our primary use case?

I am using JIRA Portfolio for tracking and reporting issues. We use it for the entire sprint and will have all the information there, such as testing, and all the developers.

How has it helped my organization?

The solution has improved our production process. We have fewer issues and everything that happens in our process is captured in the solution.

What is most valuable?

The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it.

What needs improvement?

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.

The ability to connect to market-leading tools should be easier, such as Selenium. A smaller package installation would make it easier. One component would speed up the process. For example, if people choose Selimiam in Jira Portfolio should be one component, such as one .exe file which everything can be installed. A similar process should be done for Cypress to make the process easier.

For how long have I used the solution?

I have been using JIRA Portfolio for approximately five years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

We have approximately 30 people using the solution. We plan to increase usage in the future.

The scalability of the JIRA Portfolio is good.

How are customer service and support?

We have a team that provides us with support. However, we have used support that has helped us with a few aspects, but it has been minimal.

Which solution did I use previously and why did I switch?

I have used ALM prior to Jira Portfolio. JIRA Portfolio is easier to use. When using ALM, creating tickets can be difficult.

How was the initial setup?

The initial implementation of the JIRA Portfolio was simple. We use templates for the process.

What was our ROI?

We have seen an ROI using JIRA Portfolio.

What other advice do I have?

The solution does not require maintenance.

My advice to others is to make the automation simple that is put into Jira Portfolio.

I rate JIRA Portfolio a nine out of ten.

I gave my rating of nine out of ten for the solution because it is easy to use and has benefits over ALM.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
reviewer2092605 - PeerSpot reviewer
Head of Innovation, PMO & Process Improvement at a retailer with 1,001-5,000 employees
Real User
Good flexibility, and configurability, but the interface is not user-friendly
Pros and Cons
  • "The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs."
  • "The reporting and dashboard capabilities have room for improvement."

What is our primary use case?

JIRA Portfolio is a tool that is primarily used for software development. Our scrum teams and product owners utilize it to manage the software development process. We have an extensive internal software development process that is supported by JIRA Portfolio.

The solution is deployed on JIRA's Atlassian Cloud.

What is most valuable?

The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs. Additionally, its widespread familiarity makes it easier to onboard new employees, and its associated software development tools are a major plus.

What needs improvement?

The user interface of JIRA is not very user friendly, and its configuration capabilities are limited when it comes to creating a more user-friendly experience. For example, there is no way to group fields, use bold fonts, or add colors to the interface. This is one of the main drawbacks of JIRA, as it severely limits customization options despite its general functionality.

The reporting and dashboard capabilities have room for improvement. Though there are many powerful dashboarding and reporting solutions available such as Microsoft, Qlik, and eazyBI, they may not be as flexible as desired. To maximize their utility, the ability to extract data, upload it to other tools, and use the data for reporting is desirable. Our company currently uses eazyBI as its primary reporting solution, but having the capability to upload data to other solutions using JIRA Portfolio could be advantageous.

We are working with the project portfolio and its associated reporting and KPIs. It would be helpful to have a tool that is specifically designed to track the KPIs of the portfolio. This feature should come with built-in project portfolio management processes, including KPIs, and a dashboard with preset configurations for managing the project portfolio and its KPIs. This would make it easier to work with the project portfolio and provide better visibility into its performance.

For how long have I used the solution?

I have been using the solution for one year.

What do I think about the stability of the solution?

We have had issues with the speed of JIRA's Atlassian Cloud which the solution is deployed on.

How are customer service and support?

We reached out to JIRA, our reseller, and our JIRA partner a few times over the years for support. One of the issues we had was with the speed of the cloud service, but this is a very rare occurrence. Most of the time we find what we need on JIRA's community chat and on Google.

How was the initial setup?

Setting up the new software development process wasn't a difficult task, as there was an external company with JIRA competence in Lithuania we could hire to do the configuration. However, we had to gain more knowledge about the processes we wanted to implement on JIRA. This took some time, but after a few months of learning, members of our internal team were able to configure and develop JIRA by themselves without the help of external consultants.

What other advice do I have?

I give the solution a seven out of ten.

We have 300 people using the solution.

We have customized JIRA to fit our needs in terms of portfolio management. JIRA is a powerful solution that will enable portfolio management activities to be done more efficiently. When portfolio management requires approval and process tasks, then JIRA is the right solution for the job. However, if the portfolio is more focused on reporting, then JIRA may not be so helpful and the user can continue using the tools they are currently using.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
Graziella Amaral - PeerSpot reviewer
IT Coordinator at Claro Brasil
Real User
User-friendly and customer-centric
Pros and Cons
  • "Portfolio's most valuable features are that it's user-friendly and customer-centric."
  • "Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support."

What is our primary use case?

JIRA Portfolio is used by our product teams to collaborate on projects,

What is most valuable?

Portfolio's most valuable features are that it's user-friendly and customer-centric.

What needs improvement?

The price could be improved.

For how long have I used the solution?

I've been using this solution for a year.

What do I think about the stability of the solution?

Portfolio is stable.

What do I think about the scalability of the solution?

Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support.

How was the initial setup?

The initial setup was difficult because we had issues getting a direct channel. It took around two to three months to deploy.

What about the implementation team?

We used an in-house team to implement.

What other advice do I have?

I would give Portfolio a rating of eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

PeerSpot user
Business analyst
Real User
The Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts
Pros and Cons
  • "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."
  • "Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."

What is our primary use case?

We use Jira to manage the software development lifecycle. We create a project in Jira and capture the requirements at various levels, including epics, features, objectives, stories, defects, etc. One hierarchy can have multiple levels that can be linked, so requirements are more traceable.

What is most valuable?

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. 

What needs improvement?

Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights. 

I would also like if Jira had a centralized space for accessing project-specific documents. Furthermore, they could enhance the graphs and charts to make them more presentable.

For how long have I used the solution?

We've been using Jira for around nine years.

What do I think about the stability of the solution?

Jira's code is excellent. I can quite export using Jira and smoothly use any of its features or link it with other tools to build a chart. I often use Confluence to depict our team's progress on a project. 

What do I think about the scalability of the solution?

Scalability is one of Jira's main advantages. When demand increases and an organization needs more space, Jira can support it. It provides several add-ons and connectors to link to Jira with other tools like Confluence, Excel, or various other options. We have more than 1,000 people using it.

How are customer service and support?

I have never had issues using Jira, so I've never contacted support. 

How was the initial setup?

Setting up Jira is straightforward. 

What's my experience with pricing, setup cost, and licensing?

I believe we pay a monthly license for Jira, but I don't know the precise cost. I think it's dependent on how much space the organization uses. The vendor may offer a range of pricing options based on the organization's requirements. 

Which other solutions did I evaluate?

Jira is the standard across the globe. This is the market leader for maintaining or managing software development, and it has cost advantages over other available tools. 

What other advice do I have?

I rate Jira Portfolio nine out of 10. Jira is the best tool in the market, but it still has room for improvement. At the same time, it's pretty easy to understand. There is a lot of documentation and videos online, so anyone can quickly learn various features.  

I recommend Jira Portfolio for big organizations that want to maintain the software requirements. Jira's cost may be too high for smaller organizations, but several cheaper options are available. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. partner

PeerSpot user