JIRA Portfolio Reviews

We primarily use this program as backlog management using Kanban and Scrum and also to model service tickets.

The solution has improved our organization by allowing us to create our own customization. We can track the live status of all the flows on one page and get a single view of our progress. Also, it gives us a quality overview. 

The workflow configurations, Screen filed mapping and confluence integration of this solution are what I value most. Definitely there are multiple features to support this. 

I would say that there's a lot of reporting on the dashboard so something that can be improved is the project level visibility because it is a little unclear. Especially when you compare it to JIRA Central.

I've been using this solution for around five years now on a private cloud. 

The solution is very stable.

The scalability of this program is good but it can be improved on the Administration side. 

I would say their support center is good and I would rate it a 3.5 out of 5. Every product has some pluses or minuses. So it takes a little time for things to get fixed and we always submit feedback and ask for improvements. Every product has its own backlog where we submit our request so that it gets prioritized properly. They build the product requirements based on the number of requests coming from a different client so I understand that sometimes it gets delayed.  

We currently use three solutions simultaneously, namely JIRA, Rally, and Octane. 

The initial setup was straightforward, but it is evolving towards complex now because there are many flows and many different projects. Reporting has to be done across all these projects. We use different tools for deployment.

Yes.

JIRA is a very flexible solution, so if you are a mid or small-sized team, it is very useful for the team. When you have a higher scale of work, I would say the portfolio management and the reporting need to improve. You either have to build your own solution on the APIs or you have to manage how you can configure in the current flows. My rating out of ten will be seven or eight.

In the next version, I would like to see better reporting and safer plugins, as well as easier scalability.

I primarily use the product to collaborate with the product and engineering teams. Depending on the product stage, I may draft or review the PRD, providing feedback for improvement. I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely. 

Before, I used Excel, but switching to this tool has been a significant improvement. It's much more collaborative and user-friendly. With many functions, entering and processing data is easier and faster. I can easily link documents to clients and perform tasks like inserting tables with simple commands, which helps speed up my work.

Jira Portfolio is part of our standard operating procedures to ensure product functions run seamlessly and smoothly. Providing people with sufficient tools to collaborate effectively is crucial to achieve this. Jira has become the go-to document processing tool for facilitating this collaboration and ensuring productivity. Every aspect of the product is critical for your workflow, whether gathering input from team members or seamlessly writing and managing documents.

We are based in India; I would like the product to integrate local pricing. We earn in rupees but spend in dollars. Its pricing could also be lowered. 

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

I haven't encountered any stability issues. 

I haven't contacted the technical support team personally. 

Jira Portfolio's deployment is easy. We started by signing up for the software's seven-day free trial using our credit card.  After the trial, we decided to opt for a paid plan based on the number of licenses we needed. As for any custom plans or requirements, we haven't reached that scale yet, but we know we can contact their team for further discussions when needed.

Integrating Jira Portfolio with Slack, Camunda, and other tools is part of our standard operating procedure. It helps in coordination. However, I didn't handle the integration myself. Instead, I relied on a team of more experts about the product. 

Our team has worked with the product previously and didn't need to overcome learning curve challenges. 80 percent of my organization is well versed in it. They can help people who don't know the product. I rate it an eight out of ten.

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.

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.

We are currently testing this solution with our primary use case being to deal with certain types of projects such as Cascade and Agile, as well as others that involve moving to a ticketing service, basically everything related to project management. I'm a project office supervisor. We are users of Portfolio. 

I like this solution because it has many functionalities. I love the supervision and the workflows that we can use for making a flow inside Jira. I love too, that we can take control of GitHub as it relates to project flow. Portfolio provides a good service that gives control over ticketing and control over the versions of the product. It provides resource management related to our projects.

This solution requires some effort to insert functionalities from Tempo to the base of Jira. I think that could be simplified.

I've been using this solution for three months. 

This is a solid solution and very stable. 

Portfolio is very easy to scale. 

For enterprise companies the licensing cost is fine. Those companies don't have budgetary issues. It's mid to smaller-size organizations like us that find this tool very expensive.

If you have the budget, then Jira is the way to go. 

I rate this solution nine out of 10.  

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.

We use JIRA Portfolio for management. It handles all our stories and we use the dashboards and reports. We are not fully utilizing all the features, and we use Tableau on top of it for our portfolio-level dashboards.

The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good.

The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise.

JIRA Portfolio should work on an intuitive way of querying and having different views, which will help us to track the progress. When things have been visualized they are more easily understood.

I have been using JIRA Portfolio for approximately one year.

I have not contacted technical support, but my installation or administrator team has contacted them.

I would recommend that those wanting to implement JIRA Portfolio do a smaller implementation first. Once they know the features then they can do a full-scale customized implementation for exactly what they need with the appropriate features. 

I rate JIRA Portfolio an eight out of ten.

The primary use case for this solution is to manage the work that has to be done, everything else is on a repository that is maintained by another tool.

It's how the work has been designed at the beginning of the project. We have one repository where we store all of the requirements, the testing, and all of the activity trackings are done in JIRA.

The deployment model was on-premises.

There hasn't been an improvement because we were using JIRA solutions before.

It is difficult to narrow it down to features. It's one solution as a whole and to point out certain features is complicated.

There could be many things that could be improved but we haven't been working with it long enough to accurately find the weak points.

The pricing of add-ons could be improved. You should have the option to pay only for the users concerned, that would be fine, because of the dashboards everybody has access to the dashboard.

This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing.

This solution is stable.

This solution is scalable.

I have not had any experience with customer service or technical support.

Our IT department handles this area.

Our IT department completed the initial setup, so I am not sure how complex it was.

The implementation was done through our IT department.

The pricing of the solution is expensive. 

When you install any add-on, you have to pay for each and everyone who is declared on the system in order to have the add-on working. If you have anywhere from one hundred to five hundred users and even if you only have two hundred users using this solution, you have to pay for them all.

We evaluated other options but JIRA was already in place, which is one of the reasons we stayed with JIRA.

We are dealing with several products and clients, and each product has it's good points and it's weak points.

I don't have an opinion because I think that a good process does the job and you can apply a good process to any tool. 

The tools are more and more user-friendly. Even JIRA.  

When you want to implement something, keep it simple and it will work.

With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things.  

In the end, it needs to fit the process. If the process is of poor quality, then your tool will look poor.

For the most part, with several tools, you can do nearly anything.

JIRA is a good tool. Perhaps a little bit too much to configure and adapt, because it can be adapted to any kind of customer's needs and it's not dedicated to a specific solution, but it does the job.

I would rate this solution a seven out of ten.