JIRA Portfolio Reviews

We use the solution for large-scale agile planning in our organization and ensure that every project aspect is properly accounted for, like individual products, logged correctly, and progress tracked through the portfolio dashboard. The scenario planning feature impacted your strategic decision-making.

I use this data for resource allocation, called corrective measures or actions where you can take corrective measures beyond reporting. I also use this for backlog grooming and tracking progress.

Team collaboration has been enhanced because JIRA provides a comprehensive overview of key initiatives and their respective stages. This facilitates a better understanding of the progress of tasks, whether independent teams or specific individuals are working on them. Our integration with Slack allows seamless communication, enabling us to create tickets directly from Slack, which is synced with JIRA. This feature is highly convenient for fostering collaboration across our organization's product, technology, QA, and other teams.

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.

From a usability standpoint, JIRA doesn't work properly with excessive information on the dashboard. It would be beneficial if the product team could modernize or customize the dashboard to tailor it to individual users' needs. For instance, I might only require a few key metrics on my dashboard, whereas another user might need a different information set. Introducing modularity in how information is displayed or communicated to the end user could simplify the user experience and improve overall usability.

I have been using JIRA Portfolio for seven years. We are using the latest version of the solution.

250 users are using this solution.

I did work with Monday.com. It was a disaster to manage across teams, particularly with updates from individual teams. 

The deployment is easy and takes a week to complete. There haven't been any major challenges with our IT team's new upgrade version of JIRA. As end users, we haven't encountered any challenges either. Two or three people are required for the deployment.

Deployment was handled solely by our internal IT team. We did not engage any third-party assistance. Initially, we actively participated in defining our desired user experience during the deployment phase, mainly focusing on aspects such as access, SSO integration, and other functionalities. Beyond that, it was easy.

The scenario planning feature in JIRA does have a direct impact on meeting system requirements. It assists in identifying future quarterly planning initiatives, aiding in prioritizing customer-focused tasks. This functionality consolidates numerous initiatives, helping teams pinpoint the most relevant ones to achieve specific goals. 

JIRA isn't a new framework. With multiple teams involved, including product development, finance, security, data privacy, and more, the goal is to facilitate collaboration and provide end-to-end visibility, enabling intervention whenever necessary. Collaboration and visibility are key areas of focus when developing products like JIRA. Additionally, other products, such as Monday.com, offer similar functionalities, and the adoption rate in the market depends on which product effectively meets these evolving needs.

I recommend the solution.

Overall, I rate the solution an eight out of ten.

We use the solution for software development management. It includes the timeline and the requirement definition.

As a project management team, we’re supposed to manage the teams that develop different products. It can be hectic if we don't have a tool. With JIRA, it's very easy and seamless. All the teams can give their updates, check on their backlogs, and work on them.

The ability to move across various stages from solution discovery to completion is valuable. We can assign specific tasks to users. We can also see the timeline and the progress of the projects. It makes our work easy and efficient. The tool helps us achieve more within the stipulated timeline and budget.

JIRA and Confluence must be linked automatically. What I change on JIRA must be updated in Confluence if it is related. If a task has been completed in JIRA and is mentioned somewhere in Confluence, the status must also be updated on Confluence.

I have been using the solution for one year.

I rate the tool’s stability an eight out of ten.

The product is scalable. I rate the scalability a nine out of ten. Approximately 50 people are using the tool in our organization. We are planning to increase the usage in the future.

I rate the ease of setup an eight out of ten.

I rate the pricing a six out of ten on a scale where one is cheap and ten is expensive.

Before using the solution, we were working manually. I would recommend the solution to others. Overall, I rate the tool an eight out of ten.

We use JIRA Portfolio for project management and delivery. We follow a Kanban board for new tasks, schedules, releases, bugs, and enhancements. Every new project is onboarded on JIRA Portfolio.

JIRA Portfolio is easy-to-use and has a lot of data we can track easily. The solution has good reporting and is very user-friendly. The developers can pick it up easily, and the solution's collaboration is very nice. It helps resolve a lot of collaboration issues, requirement issues, and also the metrics part. We can track the metrics straightforwardly and then see where we stand and what needs to be done.

It would be really nice if the solution provided a heads-up every time they enhance something or add new features. Recently, we had an issue because they changed the structure of using demo accounts. We didn't have any heads up and were struggling with what to do and how to go about it. We had to reach out to a lot of people, ask if they were also facing the same issue, and then we finally had to figure it out ourselves.

JIRA Portfolio is an amazing tool, but it would be much simpler if it provided a heads-up about how to go about new changes beforehand. The documentation for these changes is available online, but it's too much. If the solution comes up with a change, it should only provide information for that particular change. Otherwise, we'll have to spend a lot of time looking into a lot of documentation.

I have been working with JIRA Portfolio for four years on a continuous basis.

JIRA Portfolio is a stable solution. We've not come across bugs in the solution.

JIRA Portfolio is a scalable solution with no storage, user, or project issues. Around 18 users are using the solution in our organization.

Initially, when we had to configure the solution, we contacted its technical support team, which is well organized.

Before JIRA Portfolio, we used Microsoft Project, which was messy and painful with its Excel sheets.

The best thing about JIRO Portfolio is that its initial setup is very easy. You can start a Kanban board in a couple of minutes and then start communicating and adding users.

Our organization has seen a return on investment with JIRA Portfolio regarding the ease and the issues in managing the project or program, collaborative and documentation issues, and requirement issues. With JIRA Portfolio, there's improvement in the processes, the execution, and the delivery time.

We use a cloud version of the JIRA Portfolio.

My suggestion would be to come up with a customization plan or a business case regarding what you need for a particular project and what is possible and what is not possible with JIRA Portfolio. Then, present that business case to the technical team to avoid issues later.

I've seen scenarios where we didn't put forth a particular question and had to reconfigure and move everything to a new project. It's best to understand the project requirements and then configure accordingly to avoid such a situation.

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

JIRA Portfolio gets used by my company's customers for its capabilities, like portfolio management, project management, and generating high-level project reviews for their CXOs.

The most valuable features of the solution for my customers are the product's ability to generate dependency reports and provide the basic view where they evaluate the task status, like to which team it got assigned with respect to certain versions and how they are placed.

In general, the valuable features of the tool are its capabilities concerning dependency reports and task status.

The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA. JIRA fails to showcase particular information missing, including how resources are placed and the capacity in the coming weeks or in a particular time zone.

The product's scalability should be improved in the future. The big setback when I look at JIRA Portfolio is that though we provide multiple kinds of templates, like JWM or JSM, in place, JIRA doesn't give you an option where you can play with multiple kinds of project methodologies. If you look at the bigger picture, Atlassian gives you a box mechanism where it has an approach where it provides lean, LeSS, and waterfall as well, and that particular flavor is missing in JIRA Portfolio.

I have been using JIRA Portfolio for the last four years. My company has a partnership with Atlassian. My company is a platinum partner of Atlassian in India. I use the solution's latest version.

It is a stable solution since I haven't faced any issues. Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution a seven out of ten.

My customers are mostly enterprise-sized businesses. My company does serve medium segment clients as well. With respect to JIRA Portfolio, we get many queries from enterprise customers.

The delay in response from the solution's technical support causes us to beat around the bush to identify the exact issue. I rate the technical support a nine out of ten.

Positive

On a scale of one to ten, where one is difficult and ten is easy, I rate the initial setup an eight or nine since it is not that difficult. We can do a little bit of customization, and configuration is pretty much straightforward.

The solution is deployed on Atlassian Cloud.

The time taken for deployment depends upon the configuration of JIRA Portfolio and what its users do with it. Depending on what the customers want from the tool, it may take a day to a week.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six. The product is slightly on the inexpensive front considering its competitive feature at the pricing point it offers.

If an organization requires just the reporting or portfolio view at a high level and is majorly operating on the agile front, JIRA Portfolio is the right product for them. If a company has multiple project methodologies and wants something beyond just a Gantt view in BigPicture might be the right choice.

Overall, I rate the solution an eight out of ten.

We use it for ticketing and project planning, and documentation, mainly for ticketing, department-wise ticketing, for the creation.

The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful. 

And I've even worked with multiple analysts, like, for services, and I work on Jira. 

There is room for improvement in terms of scalability. 

I have been using this solution for five years. 

The solution is very stable. I would rate the stability a ten out of ten. Everyone in our organization use Jira. So, there are more than a thousand end users. 

I would rate the scalability a nine out of ten. There is some room for improvement.

We experienced one to two downtimes in a year. However, it was supported by our internal tech support team.

I have worked with other solutions as well but as far as my real experience, one of the best tools that they can go for is Jira.

We are using the SaaS version, so we need to set it up on our own site.

Just the user sign-up, and then the central SSO system. We have our own SSO with Microsoft Azure, so it should be pretty straightforward.

Overall, I would rate the solution a nine out of ten. It is a good solution. 

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

Version management is the most valuable feature of JIRA Portfolio.

JIRA Portfolio's configuration management could be improved.

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

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.

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

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.

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

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.

We are using JIRA Portfolio life cycle management.

The solution can be deployed on the cloud and on-premise. However, most clients choose cloud deployment. Not all of our clients have their own database.

The most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin. 

The interface JIRA Portfolio could improve.

I have used JIRA Portfolio within the last 12 months.

I have not faced any challenges with the stability of the solution.

I rate the stability of the JIRA Portfolio a six out of ten.

The scalability should improve in JIRA Portfolio.

I rate the scalability of JIRA Portfolio a seven out of ten.

Sometimes there are difficulties receiving support from the vendor. They do not answer immediately.

I rate the support from JIRA Portfolio five out of ten.

Neutral

The setup of the cloud deployment is simple. The solution has over 2,000 plugins and research is needed to determine which one is the best to use and implement.

The cloud deployment takes a few clicks from the mouse to finish. It can be done quickly.

The solution should be overall more user-friendly.

There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost.

This is a great tool for life cycle management.

I rate JIRA Portfolio an eight out of ten.

I just use JIRA Portfolio, which is available on the server.

When I develop software, there are many things and we need to check the status. Then, I use JIRA Portfolio in all areas, such as JIRA's use for tracking software issues from QAT. When we needed to check the plan of our project and manage the project status, I usually used JIRA. And if there is some field issue or customer service field issue, we gather the field issues using JIRA.

I think the solution's most important and valuable feature is its ability to track the issues. We can also check the status using JIRA, which is a good function in the solution.

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.

In the future, adding certain functions should be made easier in JIRA.

I have been using JIRA Portfolio for around ten years. I am a software developer who uses the solution. Also, I don't remember the version of the solution I am using.

I rate the solution's stability an eight out of ten.

I rate the solution's scalability a nine out of ten. It is a very scalable solution. Around 2,000 people are using the solution. In my lab, 10,000 people are using the solution.

In the future, we may change to an ARM system.

I haven't contacted customer support yet. For doubts, I talk with my infrastructure team. I think JIRA's tech support is good. I rate the solution's technical support an eight out of ten.

Positive

Previously, I didn't use a different system. I just opted for Jira.

The initial setup is easy. I rate it a nine on a scale of one to ten, where one is a difficult setup, and ten is an easy setup.

I can't comment on the time taken for deployment since I don't manage JIRA server.

Maybe there are some people who manage the server using JIRA application. I guess three people are managing the solution.

A set of people were involved in the deployment of the solution.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight. There is an additional cost to be paid for some kinds of tools.

I recommend the solution to those planning to use it. I rate the overall solution a nine out of ten.

We use JIRA Portfolio to implement the scaled agile methodology and conduct retrospectives. It's also used by us for writing bugs and managing our daily structure.

The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone.

I think the solution can improve in graphs and the analysis part.

Considering what I would like to see in the solution that could simplify my life, I would like to mention Miro. Currently, we have to visit Miro specifically to carry out PI planning.

I use the cloud version of JIRA daily for the standards and traceability of defects coming from a point. I am unsure whether I am using JIRA Align or JIRA Portfolio. However, I think it is JIRA Portfolio because it has everything developed adequately for dev track, dev caller, and dev dash. Also, it has everything JIRA provides.
I think I have been using JIRA for three years. Also, I'm not sure about the version of JIRA that we are using in our organization. Since I work for a very big company in the Netherlands, the company manages all the tooling-related matters. So, only the testers and developers have access to the version information.
I am a customer of JIRA Platform.

The integration platform for the tooling now available is very easy to use, requiring no expertise in computer science engineering or any such related fields. Simply select the desired options from the provider's interface and use the tool without the need for explicit configuration. For these reasons, I rate this solution an eight out of ten.

We use the solution for tracking stories or issues. Developers create tickets, and project managers track everything using Jira.

We can track the open stories or open issues that are there. That's the most valuable feature that I find.

The solution is stable and reliable.

It's scalable and allows for various configurations. 

I don't have much exposure to it. We use the tool to a minimum amount.

The integration needs to be done with different tools. In terms of email functionality, if we have an email, it would be helpful to provide the status updates or notes directly configured via email. 

I've used the solution for a couple of years. 

It's a stable solution. There aren't bugs or glitches. It doesn't crash or freeze. It is reliable. 

It is scalable. It's used with multiple tools as well, so we can do various configurations if we need to.

The developers use it. We have about 2,000 or more users that use it within the company.

I've never dealt with technical support. I cannot speak to how helpful or responsive they would be.

The initial setup was handled by somebody else. I can't speak to how easy or difficult the process was. 

I'm not sure how many people are maintaining the product.

I don't deal with the pricing or licensing aspects of the solution. 

This is a good solution overall. 

I'd rate the solution seven out of ten.