JIRA Portfolio Reviews

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

We use the tool to track issues and develop pipelines. We also use it for versatile projects in the IT department. It helps to track KPIs, present progress to the business with dashboards, and complete the QA team's plans.

What I like about the product is its extensive features, particularly the wide set of attributes for tracking issues. Jira Portfolio allows us to track not only the overall project but also specific components within it. This is beneficial for all stakeholders, including developers and business owners. For example, business stakeholders can track all issues, regardless of status. 

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.

I have been using the product for one and a half years. 

I haven't encountered any system issues myself. During my time with the company, we've had at least one upgrade of Jira Portfolio. 

My company has around 30-50 users for Jira Portfolio. We have around 100 licenses. 

The solution's support is good. 

We know about Jira Portfolio's work and capacity planning features. However, we do not use them. Instead, we use KPIs relevant to our business. I rate the overall solution as nine out of ten. 

I would recommend the product for IT project teams because of its stability and wide range of functionalities. Although we don't use the capacity plan feature, I recommend it. It's very useful for various purposes. 

We have integrated the tool with Lucidchart and Power BI. It has add-on functionality. 

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.

Everyone mentions tasks using JIRA. It is used for various everyday tasks, including dashboards, sprints, backlogs, and workloads.

It has been very efficient for internal communication and managing different data and work projects. It tracks the progress, the development, and more. 

It is one of the important tools and one can easily maintain and manage the tasks in JIRA. 

The workflow and bucket features are most helpful. We never have code changes without a linked JIRA case. Code changes are linked to JIRA, and you can see the code changes within Jira.

 The roadmap in our capacity planning features impacted the project management. We're transitioning from Bitbucket to GitLab and JIRA, which are linked to GitLab. This change is necessary due to this transition.

The focus will be on commits. The focus will be on checking the message, confirming drastic data as a prefix. If not, then the commit will be rejected.

The products are getting bigger. So, learning JIRA is not so easy. There is a learning curve. 

It is not easy to understand all the workflows. 

I have been using it for seven years. 

I would rate the stability an eight out of ten. Sometimes, if you have a version change, even if you follow the process of "open," "in progress," "in review," "progress class," then "closed branch," and finally "close Jira," you might only change one line of code. But you still have to go through the internal process. It's modified coaching. It still goes over the entire process in ten minutes.

There are around 500 end users in the company. 

The customer service and support are good. 

We have a standalone team for the setup. 

It provides the most functions and is very agile, lean scrum. 

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

I would recommend JIRA. It is based on Agile only. So if you want to learn JIRA, you first learn Agile office knowledge or cloud or function, something like this. Then you can understand JIRA too.

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

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.