JIRA Portfolio Reviews

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.

I'm a product manager, so I create entries covered for two products that are developed by the engineering team.

The status update function is the most valuable feature. 

The data query language needs improvement. 

I have been using JIRA Portfolio for ten years. 

Jira is a highly stable solution. I would rate the stability a nine out of ten. 

One thousand users are using the solution at present. 

The initial setup is straightforward. The integration with Slack is very good. 

Jira Portfolio is a powerful tool which is very reliable and stable. I highly recommend the solution. Overall, I would rate the solution a 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.

We work in a development environment so there are multiple changes regarding development on the software platform daily. For each change, there may be some issues and some enhancements. A JIRA ticket is created and published with other procedures that can be handled.

JIRA Portfolio has many wonderful features. It is unique in the field of IT work. JIRA Portfolio's broader application, user experience, and integration capabilities are extended if you compare it to the others. For that, it's unique.

The integration capabilities of JIRA Portfolio could be enhanced. For each cloud service provider, effort should be on both sides and bilaterally. There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio because AWS has no JIRA Portfolio integration. Hence, limiting some of the solution's possibilities.

We have been using the solution for approximately five years.

The solution is stable.

The solution is scalable, and approximately five users utilize it in our organization. We will scale further in line with company growth.

We have had a good experience with customer service and support. I rate them an eight out of ten.

Positive

The initial setup is straightforward and a cloud service, so you only need to organize credentials and configure your environment to get set up.

The pricing of the license is average.

I rate the solution an eight out of ten. The solution is good, but its integration capabilities could be improved.

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.

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.

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

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

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

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

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.

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

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

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.

I am a software developer and we use this product for end-to-end SDLC. It begins with the requirements gathering, then continues with tracking features and planning our sprints. We also use it for tracking bugs.

The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects. For example, if you create a new ticket, issue, or feature, then you classify it accordingly and you can assign it to an ongoing sprint.

You can look at the sprint backlog to see what features are planned, how many are in progress, and how many have been completed. This helps during reviews because you can get information about the velocity of the team. If somebody should leave the team for a while, or are otherwise unavailable for work, then the velocity calculations are readjusted.

Converting a task into an epic is very troublesome. As it is now, if you make the mistake of creating the wrong thing then you just have to delete it and start again. If you could convert between things such as features and tasks then it would be helpful.

I have been using the Jira Portfolio for about four years.

We use Jira on a daily basis and I cannot recall having any issues with stability.

It is easy to scale but of course, the problem is that it needs licenses. As the licenses fit into a plan, it can be kind of tricky. When you want to procure additional licenses, it is a long path.

For example, if you have licenses for 50 users and you see that you need a license for another 10, then you can't just purchase a small number. At a certain point, you have to move up to 500 users, which is quite a jump.

Currently, we have about 60 users.

I have not been in contact with their technical support team, although I do go through the community forums. I get details on new features that are going to be released and other such information, but I have not had to contact support for any specific issue.

The initial setup is pretty straightforward. Somebody who knows Agile well will have no difficulty with Jira. On the other hand, somebody new to Agile may face some problems in the beginning. 

We do not have any dedicated staff for maintenance. For the operation of it, we do have a facilitator and a scrum master who manages things for each project. However, maintenance is very straightforward. We don't need a full-time administrator working on it. A couple of people working part-time can take care of it.

Internally, people within a project may need some help when it comes to things like planning. In this case, they will get help from the scrum master.

We pay our fees annually, although monthly payments are also available.

From a developer's perspective, this tool works fine and I don't have any complaints other than wanting to convert between features, tasks, etc, when a mistake has been made in creating one.

The only advice that I have for people who are implementing Jira Portfolio is to make sure that they manage their licenses properly.

I would rate this solution a nine out of ten.

We use JIRA for project management.

We were able to implement the Kanban and Scrum methods using JIRA. That was a really good argument. We had been using the waterfall method, so this really helped us to get that out there to our general way of working.

The customized workflows we can define are very valuable. JIRA's private projects are very useful as well. There are also a lot of plugins that they provide.

I think their view needs to be more user-friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using.

There are many issues, but I would say the UI needs to be improved most. Also, some training documents need to be there with respect to their configuration. They don't have training documents easily available. You really need to figure it out by yourself. That is something they must improve.

We've been using this solution for six years.

It's quite stable. We have not had any problems.

It's scalable. We currently have 45 users, with six dev users and two people for maintenance. 

We will keep on using it. Whether we expand our use depends on our entire portfolio and the product growth that we are catering to our customers.

It's not that good. I would give it a rating of three out of five, on the basis of price. They need to add improvements because it is not as easy to reach out to these people as necessary. I would expect them to have a call center or something, but they don't have one. We have to write down our messages and send them to support. It is not easy to solve our issues.

It was definitely complex to set up. It was difficult right from the start, by applying the project setting configurations. Popping up the custom fields and relating it to the workflows was also difficult. Identifying a security policy on top of that and adding the group was really complex, too.

Deployment took almost one month's time to set it up and get started.

I would rate this solution as seven out of ten.

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.