JIRA Portfolio Reviews

We primarily use the solution for issue management.

The integration is very good. We've more or less integrated with everything including reporting and registering. 

The configuration is excellent. The solution allows for the possibility to configure to your specifications. You can define projects separately, for example. If you want to configure anything, even to do a dashboard for a specific project, or user, or to define rights, etc., you can.

It's hard to say which one feature is the most important. There are many we find extremely useful.

The workflow needs improvement.

The product itself could be improved in many ways, but at the moment I don't have anything very specific to discuss.

It might be helpful to have a simple version of the solution built for a small number of users that would be fast and have a straightforward installation process.

I've been using the solution since 2012.

The solution is really stable.

The solution is big enough for what we need. We don't use it at a large scale but have anywhere from 100 to 1000 users. 

We've never had to call technical support.

The initial setup is normal. We didn't find it very complex. Deployment can take a day or two to complete. However, a large scale project might take about a month if you get into a lot of specific configurations.

We use the cloud deployment model.

I'd advise others to start with a good analysis of the solution before implementing it.

I'd rate the solution nine out of ten.

I work in hybrid technologies. Right now I work in service management. Our software disc space uses JIRA Portfolio. I've got a DevOps team and a team that works with operations. There are different elements within service management that we use JIRA to build team plans.

The number one feature is that the product makes it easier to collaborate. I think that is the most important point even though it is not perfect. Another point is that the interface is not exactly rocket science and it is fairly easy to learn. It is very much driven towards use like Microsoft or any of the other core applications available. For project and portfolio management and in terms of incident management — things like that — it is not that complex. To rate it on a scale of one to five as to what it needs to do in this category, I'd give it a four-out-of-five.

It is easy to get help from the community. So that is also a bonus. But that is like the situation with most software now.

I think to improve the product they need to work on integration. I think what I call heterogeneous integration into other tools will be important. It would be nice to work with data modeling from any tool. From an enterprise reporting perspective, you definitely want to be able to take core data, put it into any sort of raw database and be able to manipulate it to get the information you are looking for. I think the reporting side is probably where JIRA is not the strongest product in my view. Needed improvements just boil down to an improved integration.

I know it is always going to be a challenge to add new features, but I think better integration around Microsoft or other core applications would help. I think big data warehousing is important. Enabling RPA for the benefits that can offer would help as well.

Stability is debatable because you are not doing a lot of batch management. It depends on your operating system. The benefit of using a cloud implementation is that in an on-prem solution you are always responsible for maintaining your own infrastructure, hardware, backups, doing maintenance — all of those components. But that is not really a major issue for stability.

If a product is a true enterprise product, then scalability should never be an issue. If you are not working with an enterprise then you are doing a cloud-based solution and it is definitely scalable as well.

There are probably teams of around 50 in our organization, mostly made up of end-users. Obviously we have admin people and we had OEM support. But the solution is scalable to meet our needs.

We have mostly been satisfied with our customer support experience. Customization is a bit tricky, so you have got to really understand what you are trying to achieve. Technical support was able to help us through some issues.

If I look at just on your ITSMs (IT Service Management) side, I've used ServiceNow. Also, HP Service Manager.

I do not think the initial setup was complex.

We got maintenance support from our vendor. It included time and material when we made the contract for support.

When considering the product solutions, I was looking for functionality comparisons between an SDM (Service Desk Management) BMC (Baseboard Management Controller) remedy. I'm sort of interested to understand what are the major benefits or differences between those two. I think that was really where I was trying to just get some help. I've got a team of about 169 people in the project and I was just trying to see where I could get information very quickly without having to go to the vendors. A lot of resources just house people with more questions than answers.

If you are looking for collaboration, then I would definitely recommend the product. It is one of the easiest and not very expensive.

On a scale from one to ten where one is the worst and ten is the best. I would rate the products overall as a  seven. It could not get a ten. Seven leaves room for improvement.

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.

Currently, we use the on-premises deployment model but we are moving to the cloud. Amazon is part of it but we are in the evaluation part. Our primary use case is for workflow and regression testing. 

The dashboard is the most valuable feature. The user experience is very good, it's easy to use.

The stakeholders have to decide to use JIRA and that's the problem. Not all the stakeholders are in touch with JIRA but we need their budget for the whole team to get the opportunity to use JIRA. It's not a problem with the tool, it's our organization. Some of the stakeholders have other opinions and they like to use other tools.

The initial setup could use improvement. 

Stability is very good. It's an easy to use and nice tool. We wanted to and we have bought licenses. For the bank, we have 250 users at the moment. We will increase it up to 500 users.

For maintenance, at the moment we just have a crew that takes part in the maintenance. It's only one or two people. 

We don't contact their technical support very often. Most of the things we do by ourselves, and we look for some videos on YouTube for such things. We are in a group and there we get some information about JIRA. For most things we need, we get our own information.

The initial setup was complex. We have Agile teams and we have classic teams and the waterfall development. We have to integrate both and we have to create a workflow that can be used for all of these aspects. Our governance in Germany for a bank is difficult. We have many things to keep in mind.

The deployment only takes two weeks but the difficulty is that we have many systems. Our old system is divided into 10 subsystems, so when we deploy we have to use other things. We must look for every single system. We'd like to integrate with JIRA but at the moment it's not in our book.

I would rate it a seven out of ten. I don't know everything about the solution and every feature. 

Our primary use case of this solution is for organizing our projects and as a tracking solution for our software projects.

Before JIRA, we used to organize our software with Bitbucket but now, with JIRA, it is more efficient to organize all the work in the timeline, make long-term plans for one or two months, know what our deadlines are, and write short summaries in the backlog. The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized. 

We use all of the features. The most valuable features are the reporting of the speed of the team's progress and the long-term organization of our projects in the timeline. 

I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear. Now we are using next-generation projects, so it's simpler to set the projects up than it was in the past. There is some work to be done there to have a clearer interface and workflow of how to organize a simple software project.

We have nine users using this solution. We do have plans to increase the usage. Gradually, all of the people on our team will use it and even more when a new developer or new employee comes to the company. We spend time getting familiar with JIRA then we organize the work to be done in the day in JIRA.

I only needed technical support once. We got a very specific and straightforward answer. From that experience they were good and very efficient.

We were previously using Atlassian Bitbucket. Bitbucket is only good for tracking down issues but it is not helpful to organize everything and see how fast you are proceeding. With JIRA, there are a lot more features actually managing a project.

The initial setup was straightforward. 

We have nine people using it so we have a standard cost of approximately $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher.

I would definitely suggest going for it.

I would rate JIRA Portfolio an eight out of ten. To make it a perfect ten it should have a better user interface, be more clear, and more responsive.

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.

We are in a very large company and I am an Agile Coach in our department.

All of the charts, including the Burndown chart, are very useful for us.

The graphics and the resolution of the work are very good.

The JIRA command line is also a very valuable feature.

We would like to have an option for a secure board that we can give to our clients that would allow them to see certain aspects during development, but not so much that they can steal all of our information. A dashboard specifically for customers would improve this solution.

Sometimes I have a customer-solution in addition to the more general solution. I would like to be able to differentiate these using perhaps a different color.

If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out.

It is hard to work from the bottom up. If you tap on your epic you can see its features, and if you open its features you can see user stores. If you go on, if you are going from top to bottom, it works well. However, if you want to go from the bottom up, it is very hard to do.

The stability of this solution is good enough.

The scalability is ok and we have had no problem with it.

We have used JIRA in this company for many years but we just recently started in this department. In this department, we used to use another solution.

I would rate this solution a seven out of ten.

My primary use case for Jira Portfolio is mainly resourcing capacity managements.

It allows me to do the capacity management and it allows me to qualify my ethics, and that's what the capabilities I was searching for in a solution like Jira Portfolio.

When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream.

In a PC environment, it is quite stable.

For the scalability, in my opinion, with Jira Portfolio you don't need to scale that much because it's only used by management itself.

I did not have an experience with technical support of this solution.

I was not involved with the initial setup of the product.

When evaluating a product like this, make sure to consider:

• Capabilities
• Goals
• Drives

This solution has a comparable pricing in comparison to other similar products on the market. 

We considered ALM Octane. The price of Jira and ALM Octane is comparable. We also looked at Micro Focus and CA PPM.