JIRA Portfolio Reviews

We use it for ticketing and project planning, and documentation, mainly for ticketing, department-wise ticketing, for the creation.

The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful. 

And I've even worked with multiple analysts, like, for services, and I work on Jira. 

There is room for improvement in terms of scalability. 

I have been using this solution for five years. 

The solution is very stable. I would rate the stability a ten out of ten. Everyone in our organization use Jira. So, there are more than a thousand end users. 

I would rate the scalability a nine out of ten. There is some room for improvement.

We experienced one to two downtimes in a year. However, it was supported by our internal tech support team.

I have worked with other solutions as well but as far as my real experience, one of the best tools that they can go for is Jira.

We are using the SaaS version, so we need to set it up on our own site.

Just the user sign-up, and then the central SSO system. We have our own SSO with Microsoft Azure, so it should be pretty straightforward.

Overall, I would rate the solution a nine out of ten. It is a good solution. 

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.

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.

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. 

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.

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.

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.