JIRA Portfolio Reviews

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.

We are using JIRA Portfolio for business estimates and you can attract your product in a very well manner.

The most valuable feature of the JIRA Portfolio is the many features it provides, such as code integration, documentation, roadmap, and Eclipse. The solution is useful for product managers.

JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools.

In a future release of JIRA Portfolio, they should add more general features to make it easier for project management.

I have been using JIRA Portfolio for approximately eight years.

JIRA Portfolio is a stable solution because it is on the cloud and it is one of the main reasons we chose it.

The scalability of the JIRA Portfolio is good. If you want to add more users you will only need to purchase the ability to have more users.

We have approximately 50 people using its solution in my organization. The users consist of managers, field workers, operational managers, and other teams. Everyone from junior to senior level is using it.

I have not needed to use the support.

The initial setup of the JIRA Portfolio is in the medium range of difficulty. We needed some training to be provided to our teammates. However, after the training, we were more capable. Without the training, we could not access very much or assign any product.

The setup of the JIRA Portfolio is continuous, it has taken us eight years.

We have a license to use JIRA Portfolio, we are not using the free version.

We needed complete visualization for our product which JIRA Portfolio was very capable of. As a product tracking tool, it was very good.

Whether or not this solution will be a benefit to your project depends on a lot of factors, such as your requirement.

I rate JIRA Portfolio a nine out of ten.

I'm a product manager, so I create entries covered for two products that are developed by the engineering team.

The status update function is the most valuable feature. 

The data query language needs improvement. 

I have been using JIRA Portfolio for ten years. 

Jira is a highly stable solution. I would rate the stability a nine out of ten. 

One thousand users are using the solution at present. 

The initial setup is straightforward. The integration with Slack is very good. 

Jira Portfolio is a powerful tool which is very reliable and stable. I highly recommend the solution. Overall, I would rate the solution a nine 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.

I am using JIRA Portfolio for tracking and reporting issues. We use it for the entire sprint and will have all the information there, such as testing, and all the developers.

The solution has improved our production process. We have fewer issues and everything that happens in our process is captured in the solution.

The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it.

The automation in JIRA Portfolio could improve, it takes some time. We have to do some other tactics to have the same integration. Manually integrating something will take more work than if it was automated, but the automation scripting in the solution is not simple.

The ability to connect to market-leading tools should be easier, such as Selenium. A smaller package installation would make it easier. One component would speed up the process. For example, if people choose Selimiam in Jira Portfolio should be one component, such as one .exe file which everything can be installed. A similar process should be done for Cypress to make the process easier.

I have been using JIRA Portfolio for approximately five years.

The solution is stable.

We have approximately 30 people using the solution. We plan to increase usage in the future.

The scalability of the JIRA Portfolio is good.

We have a team that provides us with support. However, we have used support that has helped us with a few aspects, but it has been minimal.

I have used ALM prior to Jira Portfolio. JIRA Portfolio is easier to use. When using ALM, creating tickets can be difficult.

The initial implementation of the JIRA Portfolio was simple. We use templates for the process.

We have seen an ROI using JIRA Portfolio.

The solution does not require maintenance.

My advice to others is to make the automation simple that is put into Jira Portfolio.

I rate JIRA Portfolio a nine out of ten.

I gave my rating of nine out of ten for the solution because it is easy to use and has benefits over ALM.

JIRA Portfolio is a tool that is primarily used for software development. Our scrum teams and product owners utilize it to manage the software development process. We have an extensive internal software development process that is supported by JIRA Portfolio.

The solution is deployed on JIRA's Atlassian Cloud.

The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs. Additionally, its widespread familiarity makes it easier to onboard new employees, and its associated software development tools are a major plus.

The user interface of JIRA is not very user friendly, and its configuration capabilities are limited when it comes to creating a more user-friendly experience. For example, there is no way to group fields, use bold fonts, or add colors to the interface. This is one of the main drawbacks of JIRA, as it severely limits customization options despite its general functionality.

The reporting and dashboard capabilities have room for improvement. Though there are many powerful dashboarding and reporting solutions available such as Microsoft, Qlik, and eazyBI, they may not be as flexible as desired. To maximize their utility, the ability to extract data, upload it to other tools, and use the data for reporting is desirable. Our company currently uses eazyBI as its primary reporting solution, but having the capability to upload data to other solutions using JIRA Portfolio could be advantageous.

We are working with the project portfolio and its associated reporting and KPIs. It would be helpful to have a tool that is specifically designed to track the KPIs of the portfolio. This feature should come with built-in project portfolio management processes, including KPIs, and a dashboard with preset configurations for managing the project portfolio and its KPIs. This would make it easier to work with the project portfolio and provide better visibility into its performance.

I have been using the solution for one year.

We have had issues with the speed of JIRA's Atlassian Cloud which the solution is deployed on.

We reached out to JIRA, our reseller, and our JIRA partner a few times over the years for support. One of the issues we had was with the speed of the cloud service, but this is a very rare occurrence. Most of the time we find what we need on JIRA's community chat and on Google.

Setting up the new software development process wasn't a difficult task, as there was an external company with JIRA competence in Lithuania we could hire to do the configuration. However, we had to gain more knowledge about the processes we wanted to implement on JIRA. This took some time, but after a few months of learning, members of our internal team were able to configure and develop JIRA by themselves without the help of external consultants.

I give the solution a seven out of ten.

We have 300 people using the solution.

We have customized JIRA to fit our needs in terms of portfolio management. JIRA is a powerful solution that will enable portfolio management activities to be done more efficiently. When portfolio management requires approval and process tasks, then JIRA is the right solution for the job. However, if the portfolio is more focused on reporting, then JIRA may not be so helpful and the user can continue using the tools they are currently using.

JIRA Portfolio is used by our product teams to collaborate on projects,

Portfolio's most valuable features are that it's user-friendly and customer-centric.

The price could be improved.

I've been using this solution for a year.

Portfolio is stable.

Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support.

The initial setup was difficult because we had issues getting a direct channel. It took around two to three months to deploy.

We used an in-house team to implement.

I would give Portfolio a rating of eight out of ten.