Coming October 25: PeerSpot Awards will be announced! Learn more

JIRA Portfolio OverviewUNIXBusinessApplication

JIRA Portfolio is #4 ranked solution in top Enterprise Agile Planning Tools. PeerSpot users give JIRA Portfolio an average rating of 8.6 out of 10. JIRA Portfolio is most commonly compared to Jira Align: JIRA Portfolio vs Jira Align. JIRA Portfolio is popular among the large enterprise segment, accounting for 70% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 20% of all views.
JIRA Portfolio Buyer's Guide

Download the JIRA Portfolio Buyer's Guide including reviews and more. Updated: September 2022

What is JIRA Portfolio?

The agile portfolio management tool, built for JIRA.

With Portfolio for JIRA, you can plan and forecast a realistic roadmap, make data-informed decisions when the unexpected happens, and keep everyone in the know.

JIRA Portfolio was previously known as Portfolio for JIRA.

JIRA Portfolio Customers

Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan

JIRA Portfolio Video

JIRA Portfolio Pricing Advice

What users are saying about JIRA Portfolio pricing:
"We have a license to use JIRA Portfolio, we are not using the free version."

JIRA Portfolio Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
RobertJacobs - PeerSpot reviewer
Principal Solution Architect at Trundl - Atlassian Platinum Solution Partner
Consultant
Top 20
Great roadmapping, reasonably priced, and good support services
Pros and Cons
  • "Having an option to view dependencies between projects and teams is great."
  • "It's got kind of a steep learning curve."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

Buyer's Guide
JIRA Portfolio
September 2022
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
634,325 professionals have used our research since 2012.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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.

What was our ROI?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Gary Craven - PeerSpot reviewer
Vice President, Consulting Services at Paradigm Consulting Group
Real User
Top 10
Powerful, flexible solution with a bit of a learning curve
Pros and Cons
  • "The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area."
  • "Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up."

What is our primary use case?

Originally, we used JIRA for help desk ticketing, but the biggest use case for the solution now tends to be supporting Kanban and scrum-based agile development.

What is most valuable?

The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area. If you look at the videos they publish on YouTube, other platforms, and internally, they support their users pretty well.

What needs improvement?

The weakness of the solution is that the interface is a little nonstandard, meaning it's very flexible. It's got a lot of power and gives the user the ability to combine different projects into the portfolio and move user stories between projects and link them. What I have found in a couple of organizations that I've used it with, is that the uptake tends to be a little slow because it's got a bit of a learning curve.

It can dump data out to Excel and those programs, but it also has a big ecosystem of plugins and add-ons that you can get. I guess it has some strength in that regard, but if you're going to run it on-prem, you have to have people that are pretty well-versed in the program and have the time and capabilities to handle integration and make sure they're adding those modules correctly.

Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. Now they are moving into these new use cases, including systems development, business projects, business processes, and redevelopment projects, but there is a problem with the nomenclature that they use, and some of the documentation is a little techy for moving it into those more business-focused use cases. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.

For how long have I used the solution?

I have been using JIRA for about three to four years.

What do I think about the stability of the solution?

The solution is pretty stable and the code is solid. I haven't dug under the covers of it particularly, but I do have some familiarity with these kinds of products and I get the sense that this solution is pretty well-designed and they've invested quite a bit in modernizing it and keeping it updated. It seems efficient. One of my latest implementations was using this solution with the Canadian government. They have a very extensive implementation of it and they haven't had any particular issues.

What do I think about the scalability of the solution?

The solution is very scalable. I think it is probably more scalable than MS project server when it is used for project management. I've seen it used in IT shops with up to 8,000 people, so it's pretty scalable.

How was the initial setup?

I'm not very familiar with the setup on-prem. My company is a consulting firm and the clients that I have worked with personally were running the solution on-prem, so they had their own technology people setting it up. I think it's a fairly straightforward thing to manage and set up. These days, Atlassian is focusing much more on their cloud version of the solution, which is probably the most straightforward way for a new user to adopt the product.

What other advice do I have?

My advice would be to carefully consider your rollout strategy, the amount of training involved, your communication, and organizational change around the use of the product. Think carefully about how you're going to use it. It's pretty malleable in that you can use it in a lot of different ways, so think that through. I suspect that Atlassian provides support in that area, but whether they do or they don't, it's something you're going to have to put some work into for a successful implementation.

Also, as far as a maintenance team goes, there's a couple of layers to consider. The people needed for looking after the system admin on the product would be very low. I think two or three people would be enough backup to make sure that you have continuity. There's also another layer of admin that is more involved in some of the setup and customization of the product for different use cases. I think you would need more people, maybe like five to ten, on that tier of supporting the users. You need that kind of support because the product is a little too technical to hand it to a project manager. Unless they're pretty well-versed in it, they are going to need some support for setup and usage in their particular application of the product.

I would rate this solution as a nine out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Buyer's Guide
JIRA Portfolio
September 2022
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
634,325 professionals have used our research since 2012.
Business analyst
Real User
The Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts
Pros and Cons
  • "Jira's Structure, agile, and Kanban boards are helpful. I also like JQuery, which allows you to fetch the relevant set of data. We use JQuery, JQL, and the Structure board a lot. Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts."
  • "Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."

What is our primary use case?

We use Jira to manage the software development lifecycle. We create a project in Jira and capture the requirements at various levels, including epics, features, objectives, stories, defects, etc. One hierarchy can have multiple levels that can be linked, so requirements are more traceable.

What is most valuable?

Jira's Structure, agile, and Kanban boards are helpful. I also like JQuery, which allows you to fetch the relevant set of data. We use JQuery, JQL, and the Structure board a lot. Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts. 

What needs improvement?

Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights. 

I would also like if Jira had a centralized space for accessing project-specific documents. Furthermore, they could enhance the graphs and charts to make them more presentable.

For how long have I used the solution?

We've been using Jira for around nine years.

What do I think about the stability of the solution?

Jira's code is excellent. I can quite export using Jira and smoothly use any of its features or link it with other tools to build a chart. I often use Confluence to depict our team's progress on a project. 

What do I think about the scalability of the solution?

Scalability is one of Jira's main advantages. When demand increases and an organization needs more space, Jira can support it. It provides several add-ons and connectors to link to Jira with other tools like Confluence, Excel, or various other options. We have more than 1,000 people using it.

How are customer service and support?

I have never had issues using Jira, so I've never contacted support. 

How was the initial setup?

Setting up Jira is straightforward. 

What's my experience with pricing, setup cost, and licensing?

I believe we pay a monthly license for Jira, but I don't know the precise cost. I think it's dependent on how much space the organization uses. The vendor may offer a range of pricing options based on the organization's requirements. 

Which other solutions did I evaluate?

Jira is the standard across the globe. This is the market leader for maintaining or managing software development, and it has cost advantages over other available tools. 

What other advice do I have?

I rate Jira Portfolio nine out of 10. Jira is the best tool in the market, but it still has room for improvement. At the same time, it's pretty easy to understand. There is a lot of documentation and videos online, so anyone can quickly learn various features.  

I recommend Jira Portfolio for big organizations that want to maintain the software requirements. Jira's cost may be too high for smaller organizations, but several cheaper options are available. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Flag as inappropriate
PeerSpot user
AMITKUMAR26 - PeerSpot reviewer
Human Resources at CollegeDekho
Real User
Top 5
Feature rich, high availability, and useful management
Pros and Cons
  • "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."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using JIRA Portfolio for approximately eight years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

I have not needed to use the support.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Flag as inappropriate
PeerSpot user
Senior Application Development Specialist at Accenture
Real User
Reliable and customizable with responsive technical support
Pros and Cons
  • "Its stability is very reliable."
  • "It would be nice if it could provide an end-to-end solution for a project."

What is most valuable?

There are several features that I like. For example, the way we can categorize the statuses of our tasks is great. We can build any number of columns to show the different status of the progress status of our task.

It is customizable and offers great integration with other products, like HP or ASD portals or any other third-party portal. 

The solution can scale.

Its stability is very reliable.

Technical support is always responsive. 

What needs improvement?

I don't much have developer insight into the Jira tool, however, it would be nice if it could provide an end-to-end solution for a project. For example, I'm from the SAP field. In SAP, we have something called SAP Chart or Solution Manager, and there you can create tickets and you can monitor the progress. You can manage the end-to-end scenario from development to go-live. If those features could be incorporated into Jira, it'll be a full package.

For how long have I used the solution?

I've been using the solution for three or four years at this point. 

What do I think about the stability of the solution?

The stability has been great overall. O haven't dealt with bugs or glitches. It doesn't crash. It's reliable. 

What do I think about the scalability of the solution?

We have found the scalability to be good. If you need to expand Jira, you can.

How are customer service and support?

Technical support has been pretty good. Whenever we face an issue, we have an email with an ID number was can share with the Jira support. Instantly we get an acknowledgment that the issue has been received and they're working on it. 

How was the initial setup?

I'm more of an end-user and therefore I was not involved in the initial setup.

What about the implementation team?

There were a few colleagues that handled the initial implementation. 

What's my experience with pricing, setup cost, and licensing?

I don't have any details in terms of licensing or costs. 

What other advice do I have?

I'm an end-user. I'm not overly technical. 

I would rate the solution eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Assyr Carvalho Junior Carvalho Junior - PeerSpot reviewer
Solutions Architect Leader at e-Core
Reseller
Top 5Leaderboard
Great management capabilities with good reliability and an easy initial setup
Pros and Cons
  • "We have found the solution to be stable."
  • "The HR aspect of the solution could be improved."

What is our primary use case?

With Jira software, I can implement DevOps. The Jira Software Management is a part of the ITSM, incident management, for the principal features of the software. It's basically used for DevOps and the ITSM.

What is most valuable?

I like the Jira Software Management. You can attend to many areas for the customer. For example, I can support IT as well as the financial areas. Jira Software Management is very important for the customers for this reason.

The initial setup process is simple. 

We have found the solution to be stable.

It is highly scalable due to the cloud.

Technical support has been great.

What needs improvement?

The HR aspect of the solution could be improved. 

For how long have I used the solution?

I've used the solution for one year. I started to work with Jira when I started with my organization.

What do I think about the stability of the solution?

The solution is very stable. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

What do I think about the scalability of the solution?

Scaling is easy as the software work in the cloud. That makes it very simple to scale the software. It's no problem.

We have a lot of users on the solution currently. 

How are customer service and support?

Technical support is good. they have been helpful and responsive for the most part.

How would you rate customer service and support?

Positive

How was the initial setup?

We have found the implementation process to be simple and straightforward. the setup is not hard. I'd rate it a four out of five for ease of use.

The deployment takes about two months. Of course, it depends on the customer and varies a bit. 

What's my experience with pricing, setup cost, and licensing?

I do not have any knowledge of the licensing cost.

What other advice do I have?

We are just customers. We don't have a business relationship with Jira.

It's important to know about the database. It is important to know about databases for implementing Jira Software Management.

I'd rate the solution a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Meeta Lalwani - PeerSpot reviewer
Lead Product Manager at a tech vendor with 5,001-10,000 employees
MSP
Beneficial customization and project management capabilities
Pros and Cons
  • "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."

What is our primary use case?

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

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

I have been using JIRA Portfolio for approximately seven years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How was the initial setup?

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.

What about the implementation team?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
PankajKumar12 - PeerSpot reviewer
Data Engineer at a media company with 10,001+ employees
Real User
Top 5
Reliable with great features and helpful technical support
Pros and Cons
  • "The initial setup is simple."
  • "If you want to generate a report for individual usage, it's difficult."

What is most valuable?

The initial setup is simple. 

It is very scalable.

The product offers good stability.

Jira has many features that companies can explore to see which ones are best for them and their internal needs. 

Technical support has been good so far.

What needs improvement?

I haven't seen many drawbacks on the Jira side. 

If you want to generate a report for individual usage, it's difficult. The reporting can be improved.

For how long have I used the solution?

I've been using the solution for almost two years. 

What do I think about the stability of the solution?

Its stability is great. We don't deal with bugs or glitches and it doesn't crash or freeze.

What do I think about the scalability of the solution?

The product can scale if you need it to as a company.

How are customer service and support?

We are satisfied with the technical support. Overall, I find them to be quite helpful. They are good.

How was the initial setup?

The implementation is straightforward and simple. It's not difficult at all.

If you have a cloud-based solution, you only require four or five staff members to maintain the product.

What about the implementation team?

We had the assistance of an integrator when we set up the solution initially.

What's my experience with pricing, setup cost, and licensing?

We pay a yearly licensing fee. Everything is included in that price. There aren't extra add-on fees to take into consideration. 

What other advice do I have?

We are a customer and an end-user.

I'm using the latest version of the solution. 

I would recommend the product. Companies can use it without having to worry about any hiccups. 

I'd rate the product as a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free JIRA Portfolio Report and get advice and tips from experienced pros sharing their opinions.
Updated: September 2022
Buyer's Guide
Download our free JIRA Portfolio Report and get advice and tips from experienced pros sharing their opinions.