JIRA Portfolio Reviews

The solution is simple to use. We use JIRA Portfolio with Azure Logic Apps, and it is easy to integrate them.

The solution should provide a monitoring interface for the customers to have more information about the issues. We cannot receive the information by mail. We can use the tool to share reports, but it should also have a space for customers to add comments. JIRA should provide more online video resources explaining how to use the solution.

I have been using JIRA Portfolio for one year.

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

Overall, I rate the solution a seven out of ten.

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.

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

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. 

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

I have been using JIRA Portfolio for nearly 15 years. 

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

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. 

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. 

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. 

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. 

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.  

I use the solution in my company for project management, especially when we have agile projects. My company has used the tool for planning, tracking, and action.

I have had little exposure to the tool, so I cannot speak about what needs improvement. I have used the product on a very minimal basis.

As there are no perfect solutions and considering that I rate JIRA Portfolio's stability an eight out of ten, I feel it is an area with certain shortcomings where improvements are required.

I have experience with JIRA Portfolio. I have not used it very actively. I use the tool on and off.

Based on my limited exposure to the product, I rate the tool's stability an eight out of ten. I haven't faced any problems with the product's stability.

It is a good scalable solution that I have used for small projects and reasonably large projects.

In my organization, there are teams consisting of 15 to 20 members who use the product.

I have not used any other solutions in the past for purposes similar to what I currently use JIRA Portfolio for in my company.

The product's initial setup phase was pretty okay, so it was not too bad.

In terms of the product's ability to improve the productivity of teams in our company, I would say that we have found it useful when we have to deal with projects, specifically agile projects, where it served to be very useful because it was directly applicable for planning and tracking.

I recommend the product to those who plan to use it since it is a useful solution. For my company's work, the solution had all the features we wanted, which is why we were happy with it.

The benefits associated with the use of JIRA Portfolio revolves around the fact that it is a good project management tool for our company, as it was helpful in managing our project activities.

I rate the product a nine out of ten.