JIRA Portfolio Reviews

We use the solution for tracking stories or issues. Developers create tickets, and project managers track everything using Jira.

We can track the open stories or open issues that are there. That's the most valuable feature that I find.

The solution is stable and reliable.

It's scalable and allows for various configurations. 

I don't have much exposure to it. We use the tool to a minimum amount.

The integration needs to be done with different tools. In terms of email functionality, if we have an email, it would be helpful to provide the status updates or notes directly configured via email. 

I've used the solution for a couple of years. 

It's a stable solution. There aren't bugs or glitches. It doesn't crash or freeze. It is reliable. 

It is scalable. It's used with multiple tools as well, so we can do various configurations if we need to.

The developers use it. We have about 2,000 or more users that use it within the company.

I've never dealt with technical support. I cannot speak to how helpful or responsive they would be.

The initial setup was handled by somebody else. I can't speak to how easy or difficult the process was. 

I'm not sure how many people are maintaining the product.

I don't deal with the pricing or licensing aspects of the solution. 

This is a good solution overall. 

I'd rate the solution seven out of ten.

We use JIRA Portfolio to implement the scaled agile methodology and conduct retrospectives. It's also used by us for writing bugs and managing our daily structure.

The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone.

I think the solution can improve in graphs and the analysis part.

Considering what I would like to see in the solution that could simplify my life, I would like to mention Miro. Currently, we have to visit Miro specifically to carry out PI planning.

I use the cloud version of JIRA daily for the standards and traceability of defects coming from a point. I am unsure whether I am using JIRA Align or JIRA Portfolio. However, I think it is JIRA Portfolio because it has everything developed adequately for dev track, dev caller, and dev dash. Also, it has everything JIRA provides.
I think I have been using JIRA for three years. Also, I'm not sure about the version of JIRA that we are using in our organization. Since I work for a very big company in the Netherlands, the company manages all the tooling-related matters. So, only the testers and developers have access to the version information.
I am a customer of JIRA Platform.

The integration platform for the tooling now available is very easy to use, requiring no expertise in computer science engineering or any such related fields. Simply select the desired options from the provider's interface and use the tool without the need for explicit configuration. For these reasons, I rate this solution an eight 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.

Advanced Roadmaps is part of Jira's premium cloud subscription, so it's bundled with the product on the cloud. They've recently included it with Data Center and they've sunsetted the server product. As of today, you couldn't go out and just run the self-hosted product with a server license. They stopped sales of those and support for those.

Jira's got a family of three products. Jira software, which is used by mostly engineering team teams or software development teams. Then they have a help desk solution called Jira Service Management, which is used primarily by IT support folks. They can take in requests. Now, with the advent of Enterprise Service Management, you're seeing more help-type projects for folks. And then Work Management, the last of the three. Usually, most business teams work out of that. You might have marketing teams as well. They don't need all the software features. As a part of the premium package, you get a planning environment, which enables you to plan across projects, not just at the project level in what was formally called Portfolio for Jira. That's now called Advanced Roadmaps. They rebranded it a year or two ago to Advanced Roadmaps. It used to be sold separately. You'd get it as a separate cost and you would install it. It's plug-and-play. It would work on top of everything you already had. Since it was their own product, Atlassian decided to bundle it with the premium tier rather than having every tier including it.

Mostly there are two kinds of thought processes. A lot of people are still transitioning from waterfall. They really want the kind of Gantt chart view of the data. That's what's referred to as the roadmap in Advanced Roadmaps.

The other thing that's popular and implemented is the dependencies. Having an option to view dependencies between projects and teams is great. You might have to work to resolve those, remove those kinds of dependencies, or just be aware of them that they exist and coordinate the work between teams. Those two features are the main things. They like the Gantt chart views and also like seeing the dependencies on the dependency port and being able to forge those relationships in that environment too.

It's hard for people to learn. It's got kind of a steep learning curve.

As much as it's not Excel, I would like to see an auto-scheduling feature. It'll help you plan, yet it won't plan for you. Some people think of it as an easy button they'll hit. They have this feature already, auto-schedule. And if you understand it, you know what to do before you auto-schedule the work. If you've manually set a due date on something, it's going to respect that. It's not going to try and override it when it auto-schedules it. However, what I thought would be pretty cool is if there was the ability with these planning environments that one could introduce their own scheduling algorithm. If you carry that one step further, if it comes pre-configured with these relationships and how the auto-schedule will run, that would be ideal.

I’d like to have an algorithm or a way to introduce our own scheduling algorithm. Whether that is just a GUI for that that allows you to say, "Hey. Let's prioritize based on certain criteria," or something else, that would be ideal. There needs to be some more flexibility in the scheduling.

All of the data lives inside the tool. So maybe it could use some more integration or export options to formats that are common, like Excel or PDF or something.

However, I've run into a lot of research where people handle complex multi-level projects. That's a whole different subject matter domain. A lot of people look at is the best algorithm to auto-schedule work or predict where they may end or start based on those type types of formulas. The other thing that I liked yet went away is the resource management piece. It'd be great for a planning tool to look at the individual level, not just the team level, at the individual's skillset for planning purposes. Hopefully, we would have more data points. Their availability, capacity, for example, what days they'd be available to work, et cetera, could be tracked. This is something that they started with. They had this concept and then Atlassian said it wasn't getting much use, so they decided to pull it from the product.

I've been using Jira products since about 2008. It’s been 15 years now.

If you go with the self-hosted option on Data Center, you still have all the support. If there are bugs encountered, sometimes that can be a long time before those are resolved. However, you get the latest features and updates in the cloud automatically. Any bug fix that they identify is immediately addressed.

The scalability is great. Atlassian hosts from ten to 10,000 users in a cloud. If you go with the self-hosted on-premises, their products are also designed to scale. They've tested up to hundreds of thousands of users.

It is somewhat underused right now. I don't see a lot of plans in there or people that aren't using it. It's more based on the organization's maturity and our own maturity and if they will find a use for it. If they're just starting out and it's a small team, typically, you won't see any use. However, as the company begins to grow, and they start realizing that, "Oh. This would be good to do a process teams,” then you'd see more of a use case for it. However, for the smaller companies, it's definitely underused. Larger companies are starting to poke around in it since they realize the value it would have.

Mostly since they are built and maintained by Atlassian, there's seldom a moment when you encounter an issue. Mostly it's a suggestion or a feature request that gets reported as a bug, yet it's not. It's actually something that somebody wants to work in a different way. Overall in both cases, it's well supported.

Customer service is very good. Sometimes what people complain about is the lack of consistent representation. Anytime you call in, you're going to get somebody new. However, they're generally very responsive.

They do have a tendency to deflect a little bit. For example, they will ensure they don't fully engage with you unless the ball is truly in their court. They're not going to show you how to use the product or things like that. They'll tend to send you a knowledge article.

If you are genuinely stuck, for example, you encounter an issue or something like that, they're responsive and get on top of those things right away.

The support is friendly. If you're having an existing problem, you won't necessarily have the same representatives with all the context and everything.

The clients have a couple of products that are usually installed, sometimes even side by side with Portfolio for Jira, for example, BigPicture. That is an add-on. Still, it's not made or maintained by Atlassian. That's a third-party vendor. However, they built it on top of the code, the same tool. The structure is another third-party marketplace app.

Jira Align is also owned and maintained by Atlassian. However, it is a separate product and you do have to have the right fit for it. It's a purpose-built, agile-at-sale solution. It's not something that they market to smaller organizations or teams.

The initial setup is complex, as much as they've made a lot of strides to improve that. They've removed some of the complexity by taking certain features away from it. It kind of runs to help you set up your initial plans. However, to get the maximum value from it, you need training, and you need to be experienced in its use and understand how that algorithm works, which isn't really taught or known. You just kind of learn through experience. There is that learning curve, and it's very steep.

In terms of the deployment, it comes installed out of the box. If you get any of the cloud subscription premium tier, it's already pre-installed. That's true also with the newer versions of Data Center. If you've been using the products for some time, you would've had to install them from the old marketplace app. That wasn't so bad. It’s plug-and-play. It's already been tested and it's compatible with the system. There are just some manual steps you would need to go through to install it if you're using an earlier version.

It's built and maintained by Atlassian. It's very stable. It complies with all of their SLAs and support that they offer when it's the Atlassian-hosted subscription.

Clients implement it themselves. It's part of the core product. It's extending it. You can start a free trial and spin up a new one. You can try out the premium version for free for a couple of weeks. That's something that any user would be able to do. However, when we get involved as a consultant, it is usually when we have to go in align things. Maybe they didn't understand it and started making changes to the system and need somebody to help them and guide them through it. That said, generally speaking, a customer wouldn't need to get somebody to do the integration for it.

In terms of ROI, getting to it is usually pretty quick, unlike ServiceNow, which is usually a long time to set up and configure. Often you have to engage a consultant. With these tools, especially the SaaS version, you just quickly get going. You don't even have to give a credit card. You sign up, and you have a site that's up and running. And that's across the different family of products, even their service desk is positioned that way. One of the advantages they claim is it's so easy to get up and running, as opposed to some of their competing tools out there that require a lot of configuration on the backend or what have you.

They have a subscription model. If you're on the premium tier, that includes Advanced Roadmaps. This is similar for Data Center, which is self-hosted. A lot of companies will use the infrastructure as a service, AWS, or Azure to host the products in the cloud.

The licensing is very transparent. You can go to the Atlassian pricing calculator. You could get, depending on the number of users and the products and the tiers, the premium tier that has this feature set, and you can get a quote directly.

There are no hidden fees or extra charges. They're very transparent about their pricing. It's supposed to be very competitive with something like ServiceNow. ServiceNow would be ten times as much the cost per user annually as opposed to an Atlassian Jira product.

There may be some additional costs. Somebody needs to configure this and maintain it. Oftentimes you'll see a dedicated resource or resource responsibilities with a team within the organization to build those projects and help people plan. Otherwise, that's outsourced to consultancies like my own company. They have infrastructure costs also if you decide to host it yourself, either on-prem or in the cloud. AWS costs would not be included. You would have to pay for the hosting servers and the technical know-how and resources to manage them there. That would be the only additional cost.

You can also buy a premium support package. It's incentivized with shorter timeframes on getting back to you and getting resolutions. For larger companies, they have a technical account management program. You could purchase time with an Atlassian resource to strategize around your deployment in the ecosystem. You could get that inside scoop or whatever from Atlassian on your product roadmap and how to best get value from it.

We are integrators, partners, and resellers.

If an organization doesn't meet the minimum footprint for a product like Jira Align, which would be they would have to have a mature scrum or agile practice across, I'd say, a minimum of five teams, yet they're still looking to scale agile beyond the team level in Jira, we'll suggest Advanced Roadmaps, which was formerly called Portfolio for Jira.

That gives the company an option to work in between Jira and something as big as Jira Align and begin to prepare to scale agile so they can get those teams orchestrated through planning and events and long-term planning, and start adopting agile ceremonies and so on by using just Jira with the Advanced Roadmaps feature.

The most important thing for Portfolio is to learn how the product is intended to work and take a considered approach. Users need to be mindful of how they will plan across teams and the taxonomy or vocabulary that will be used within your organization. Those types of things will help with the configuration and change management aspects, which are also so foreign. Someone needs to take credit for everything and must be prepared to guide teams in their use for a while. There may be skeptics too around the new tools. Therefore, it's sometimes helpful to share use cases and studies from other companies in your industry. Change management aspects are part of any new tool, which is why I would say that they should have a strategy for their change management and also have a strategy or considered approach for how they're going to implement them so that everybody's on the same page.

I’d rate the solution eight 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.

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.

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.

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.