JIRA Portfolio Reviews

Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated.

We sometimes have issues importing and exporting Spanish data because we use accents, and they don't always export correctly.  

The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client. 

We've been using Jira Portfolio for one year.

Jira Portfolio is highly scalable. You can manage user connectivity and add more licenses within the tool. It's very simple and easy. We have no plans to increase usage, but the company can add more users if needed.

All our issues were solved, and Atlassian support was excellent.

Setting up Jira is simple for the user. The initial implementation takes about one week, and the sandbox can be deployed in less than a month. I handled it all myself, but there are 10 people on our IT team.

I rate Jira Portfolio nine out of 10. 

Our primary use case is to establish agile teams and Release Mgmnt process. Jira was implemented, and also Portfolio but each team manages the app as they wanted. The tool is very open, which leads to a lot of error, confusion, and end problems. Then we set up a rule to manage it, based on best practices but if someone made an error therewas no way to avoid it. It is important to have a clear methodology from the company prior to start to use a tool like Jira.

It was very easy to load tasks, assign responsibility, due dates, etc. Also, it is easy to make follow-ups. The problem is that there is not a log to track how many times the same issue was created or how many times the issue changed the due date. This is a problem when you want to improve the way of work of your team. 

Additionally, with Jira Portfolio, we had the possibility to track all the projects in the old way with some gannets but you need to be very careful with the filters. One wrong filter and the data is totally invalid

The way to manage cards as a Kanban is really easy but when you need to track hundreds of projects, you need to be very clear in which way the things must be completed. The versioning for coding the developments for me should be more restrictive. It must be set up in an alphanumeric and unique code for new developments, new functionalities, correctives, and evolutions.

There should be two ways at least to distinguish what is a technical task that will be used for Release (meaning to be deployed into production environments).

Some "help" on each tab should be included in the tool, for those people who do not have previous experience with it like how to filter part of the portfolio or project, how to easily set the versioning based on Release management best practices, and in my opinion, nobody should delete a task inside the team. There should be a log to track all movements of cards, any change on dates, due dates, responsibilities, etc.

Another thing could be to have an easy way to manage the Portfolio and have more ways to share and to show graphics and reports

We have been using JIRA Portfolio for nine months. 

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.

We use JIRA Portfolio to manage our program of work.

Since we have been using JIRA Portfolio it has improved our productivity and visibility.

The most valuable feature of JIRA Portfolio is the visuals it provides rather than Kanban boarded tickets.

I have been using JIRA Portfolio for approximately two years.

The solution is reliable.

We have approximately 50 people using the solution in my company.

We had to use assistance for the initial setup.

We used a third-party implementation to develop the solution.

I rate JIRA Portfolio a six 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.  

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.

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.