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 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.

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.

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.

I mainly use Portfolio for integrating systems, such as web pages for different brands. We also use it for loyalty and analytics applications.

Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company.

Portfolio's best features are performance and elastic memory.

An improvement would be if Portfolio were integrated with Office 365. Also, Portfolio's portfolio management is complicated because you need different components or apps to see specific portfolios. 

I've been using Portfolio for three years.

Portfolio's stability is good.

Portfolio is scalable for some things, but it's more difficult if you need to scale a whole company in other levels.

JIRA's technical support is very good - when I have a question or a problem, they give us the solution immediately.

Neutral

The initial setup was easy, and deployment took a couple of months.

We used an in-house team.

Portfolio is well-priced - a license for ten users costs $100 or $150 a month. There are no additional fees to pay.

Portfolio is user-friendly, and the escalation in the organization is faster and better. I would rate it as ten out of ten.

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.

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. 

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.

We've been using Jira for around nine years.

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. 

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.

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

Setting up Jira is straightforward. 

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. 

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. 

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. 

The primary use case is project management. 

The entire features that are required for managing the product's communication between the team there are valuable. Managing product development and managing inter-team communications are also valuable features.

Maybe integration with other tools could be made easier. 

I have been using this solution for three years.

I would rate the stability a nine out of ten. There was no downtime, no issues.

It is a scalable solution that's suited to our requirements for small teams. I'm not sure about larger teams. So, it's limited to whatever users it has. So that's suited to our requirements.

I would rate the scalability an eight out of ten, as far as my experience goes with the tool, but I haven't used it on a larger scale.

I never needed any support. I'm a primary or maybe average user, so nothing extensively that I've used. So I have never needed any support.

It was absolutely easy to set up and work with Jira, so that was absolutely easy.

Jira is a SaaS solution, so there is nothing to be deployed. It's an on-cloud solution.

Currently, I use the free version for personal use.

I find it simple compared to Azure DevOps. Comparing both Azure DevOps and Jira, then Jira is simpler compared to DevOps.

Overall, I would rate the solution an eight out of ten. It is a good tool and easy to use. It is very easy to start using the tool. It is very easy to understand and use the tool.