JIRA Portfolio Reviews

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.

I use the solution in cases when I need to report something such as escalating a scale. 

The solution includes good and fast notifications for other project team members. 

The solution's look and feel could be a bit more intuitive and user friendly. 

I have been using the solution for one year. 

The stability is rated an eight out of ten. 

The scalability is rated a seven out of ten. 

The technical support is good so is rated a nine out of ten. 

Positive

It is important to learn about the solution's functionalities and features to prepare for use. 

I rate the solution an eight out of ten. 

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.

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.

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.

The solution’s pricing could be reduced.

I have been using JIRA Portfolio for 20 years.

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.

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

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

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.

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

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.

Our primary use for this solution is issue tracking and planning.

This product has helped our organization by allowing us to stop using Excel. We now have one team source as a centralized database. We no longer have to reconcile data or deal with differences in multiple sources.

The best feature for us is that it is a centralized database. Everyone has access to it. It is a single source of tools. We no longer have to clumsily copy and reconcile Excel spreadsheets.

Generally, I'm a happy customer when it comes to this product. The product's speed could be improved. However, there is really no software that can ever be fast enough. I would like to see more flexible reporting and the ability to customize reports. If the pricing could be reconsidered by the company, that would be helpful to all users and organizations using the product.

On a scale of one to ten, one being the worst and ten being the best, I would rate JIRA Portfolio as an eight. That is based on German skepticism. To be a ten is not even being a silver bullet, it's being a gold bullet. Very rare if it even exists. The only product I use that is a ten is TeX (or LaTeX). It is public domain software, 30 years old, absolutely stable, it never crashes, it uses a minimum amount of resources because it has no GUI. That is as close to perfect as a product can be.

The product is very stable.

The potential for scaling the product is really good. The only real limitation is the pricing. The more you want to use, the more you have to pay, and the price increases over time.

We now have more than a thousand people in IT. Our company is around 130,000 people.

Personally, I have never had any problems with the product so I am not familiar with the technical support.

We previously used Excel, which is not a solution. We were a new company at the time and it was easy enough to manage through Excel. When our needs grew and it was impossible to use Excel, we changed to JIRA as a robust solution which we could use globally in our company.

The IT department in our company did the installation and set the database up for us so I had no real involvement in the setup.

We did not use consultants or a vendor team. We have a large in-house IT staff that did the deployment.

JIRA was inexpensive in the beginning when we first took the solution on. After we bought it, the prices went up. Scaling it as our company grew was a little like making purchases from a drug dealer: once you are hooked you pay whatever you have to. Atlassian is not the only company to raise their prices over time, so it is understandable. But it is much more expensive for us now.

I like JIRA portfolio the most out of any tool I use for my job. It is my most favorite tool. It was easy to get used to using it and I highly recommend it. Personally, I say: use it. Go for it. Don't bother using other tools.

Realistically, it is good to look at the other options in the marketplace. There are many companies around offering add-ons, plug-ins, and applications that are quite good. 

The biggest lesson I have learned in using JIRA is that you should not start with Excel. It is a good idea to evaluate your business plan and look forward to growth by choosing the right solution.

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 solution to create a unified roadmap that allows us to track investments and actuals. Additionally, we need a single view that displays the work items assigned to each value stream, and we need to prioritize these items according to the WSA technique.

The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects.

The reporting has room for improvement. We were working on a project, trying to figure out what our task was and when the start and end dates were. This wasn't too difficult, as we had all the information we required, however, we had to align a lot of data in order to get the right information, which was a bit of a hassle.

The initial setup could be more user-friendly. Additionally, it's important to consider portfolio-level metrics. Having more portfolio-level metrics would be beneficial.

With Jira, an issue that arises is the length of time it takes to show certain data. If this could be sped up, the user experience would undoubtedly be improved.

I have been using the solution for one year.

We have some issues with the stability.

The solution is somewhat scalable.

Tech support can be reassuring but requires some effort to get the answers we need. We have to search through conference pages to find solutions, which may take some time, but we can purchase a service that provides ongoing support.

The initial setup is not straightforward. 

We don't take a big-bang approach. We start by deploying one piece of art and then presenting it to the leadership. They need to have an overall view of how it's progressing. If all the necessary data is available, it may not take more than two weeks to implement.

To properly implement, it was important to first tag the teams and their respective tasks and to assign them to the relevant ethics. Additionally, it was also important to set deadlines for the completion of the tasks. One of the biggest challenges is people not putting in their estimates, which hinders accurate tracking of progress.

I give the solution a seven out of ten.

We have one person per year using the solution.

JIRA Portfolio is one of the best tools for storage management. We use it in our data center.

The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability.

We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version.

I have been using JIRA Portfolio for approximately seven years.

JIRA Portfolio is stable. Initially, there were hiccups, but more or less they were stabilized later. Within the initial six months, we saw that there was some performance challenges or stability problem, but I'm not seeing any stability issues at this time. It's a great tool from that perspective.

JIRA Portfolio is scalable to a large extent because for an organization like ours, we have data that is approximately 10 years old and we migrated everything to this tool and it was able to handle all that data. 

We have approximately 3,000 users using the solution.

JIRA Portfolio's initial setup has a learning curve, but once you start using the tool, it becomes simpler in the way it is managed.

We have a team of approximately 10 who handle the maintenance and support of Jira Portfolio.

The initial learning curve should be faster and there should be quick start videos because sometimes the new users become confused. When we compare feature to feature with the tool they need some training. If we have some training while we are deploying it, it will help in the long term and remove any confusion.

I rate JIRA Portfolio a ten out of ten.