JIRA Portfolio Reviews

With JIRA Portfolio, you can do your portfolio after projects and right away you are able to see all the tickets of your portfolio. You can change the project which belongs in the portfolio at any moment and you can do any simulation you want. You can have many scenarios, and, when we agree with the scenario, we can push the scenario inside to JIRA.

The documentation is very well done.

Today, when we want to prepare PI planning, we have a dedicated plugin, which allows us to print a ticket. We have beautiful tickets which is an advantage. We can print tickets and put them right on the wall. It's better for PI planning due to the fact that you can read information, and it's always written in the same way.

On each ticket, you can see priority, version, et cetera, always written in the same way. If you write it directly, however, it's not always readable. JIRA Portfolio can help you during PI planning because you can write your dependencies directly. 

However, it would be better if you didn't have this manual part of the process. If we don't have to print a ticket and to put a ticket on the wall, it would be easier. It's very difficult, for example, for sizeable companies to find large rooms to do PI planning.

With coronavirus, we have to work from home. PI planning needs to be re-imagined. It needs to be virtual, not physical. It would be better if it was more like Klaxon, where your ticket is pushed to a blackboard.

JIRA is very poor at reporting.

I've been using the solution since the beginning of this year. It's been just over six months.

We introduced JIRA in 2018 and since then we haven't had any issues with stability. In my opinion, two years isn't a sufficient amount of time to really gauge stability, however, that said, it's never given us trouble.

We have about 2,000 people in the company using the solution.

We have reached out to technical support in the past, however, we prefer to use Google or search the forum. In fact, if you send a request to Atlassian, it's like throwing a bottle into the sea and waiting on a response. If I send a ticket directly to the expanded portal, I have a response 24 hours later, and if I send a ticket to Atlassian on JIRA Core, I'll get a response maybe one month later. It's easier, therefore, to search for a solution yourself than to expect a response from Atlassian.

In order to set up the solution properly, you need proper training first.

We have created a system inside our company. I do a sort-of training for JIRA Portfolio. I have coached about 1,000 people. I would estimate that you need two hours of training for a JIRA team member and two additional hours for a JIRA administrator, or a project administrator, and about two additional hours on top of that for JIRA Portfolio. If we set up, it takes one day. And of course, after setup, users will have to practice on the system to get used to it.

We compared five different products last year, including JIRA Portfolio, BigPicture (which is another plugin available on the Atlassian marketplace), JIRA Align, and a Micro Focus Solution. We also looked at Planview, which we already use to forecast for budgeting purposes.

We chose JIRA Portfolio for two reasons: firstly, due to the fact that it was connected directly with to JIRA, so we have a direct synchronization between BigPicture and Jira Portfolio, and secondly because you don't have to really plan anything to make it happen.

The difference between JIRA Align and JIRA Portfolio is that JIRA Align is for a large company, for example, a multinational and when you want to aggregate several JIRA instances. As we have only one Jira instance, it's more accurate for us to take on something like JIRA Portfolio.

In general, we are on a server configuration and not a cloud solution. That means, each year we have that specific version until we update it. I suppose since we have installed the JIRA Portfolio in January, it's the last version. However, I'm not sure.

I'd rate the solution eight out of ten overall.

If the solution would work for others depends on the size of their company. 

If we had to do the implementation again, we should have bought JIRA Portfolio at the same time as JIRA Core. I think we did a mistake by introducing JIRA Portfolio without it. When you buy JIRA Core, you have only three levels of subtask stories and epic in JIRA, and it's difficult for us to have only three different levels. With JIRA Portfolio, you can have as many additional levels as you want. We adopted a scaled agile model with squads and tribes. We need to implement a safe model instead.

We've since introduced, as a pilot, two additional levels as we believe it's better to have all level you need at the beginning of your project.

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.

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. 

We are using this solution to manage an agile project. We are putting JIRA on our backlog, and we are following the work in progress with the Kanban board. 

We have generated a lot of dashboard in-reporting with JIRA Portfolio to monitor the performance of our direction and our projects team. We have a license for 250 users, and we are going to get a license for 500 users. 

The feature that we like the most is that JIRA enables modules. 

Atlassian provides a lot of products around JIRA, such as compliance for the documentation, BitBucket for the Git version. We are new to these products developed by Atlassian, but they can integrate very easily. Generally, when an editor is developing a solution, they think about integrating with JIRA. When we are looking for any other solution, they plan to easily integrate with JIRA. 

We would love to be able to have direct contact with Atlassian. Currently, they are not working directly with West African countries. We are considering using JIRA Align, but when we contact them, they say that as we are in West Africa, they don't directly work with West Africa.

We have been using JIRA Portfolio for about four years, since 2016. 

It is very stable. We had only one issue, but it was not related to JIRA. 

We didn't have to get in touch with the support team. Generally, when we have an issue, we go to the community, and we are able to resolve it very fast.

The initial setup is straightforward. 

The deployment is very easy. We easily do it ourselves without any help. We have a team of two to three people.

Doing digital transformation is difficult. It's not regarding JIRA. It's difficult to change the mindset of our teams to be more agile and to adapt JIRA as a new way of working. We have to change the mindset and the mentality of the teams with a new way of working so that we can move forward. JIRA will help us to be more agile because JIRA is built for agile teams.

We had to work with a consulting team based in France to help us with the organization of the process. Atlassian doesn't directly work with West African countries. So, we had to work with a French company. 

I would rate JIRA Portfolio an eight 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.

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 this program as backlog management using Kanban and Scrum and also to model service tickets.

The solution has improved our organization by allowing us to create our own customization. We can track the live status of all the flows on one page and get a single view of our progress. Also, it gives us a quality overview. 

The workflow configurations, Screen filed mapping and confluence integration of this solution are what I value most. Definitely there are multiple features to support this. 

I would say that there's a lot of reporting on the dashboard so something that can be improved is the project level visibility because it is a little unclear. Especially when you compare it to JIRA Central.

I've been using this solution for around five years now on a private cloud. 

The solution is very stable.

The scalability of this program is good but it can be improved on the Administration side. 

I would say their support center is good and I would rate it a 3.5 out of 5. Every product has some pluses or minuses. So it takes a little time for things to get fixed and we always submit feedback and ask for improvements. Every product has its own backlog where we submit our request so that it gets prioritized properly. They build the product requirements based on the number of requests coming from a different client so I understand that sometimes it gets delayed.  

We currently use three solutions simultaneously, namely JIRA, Rally, and Octane. 

The initial setup was straightforward, but it is evolving towards complex now because there are many flows and many different projects. Reporting has to be done across all these projects. We use different tools for deployment.

Yes.

JIRA is a very flexible solution, so if you are a mid or small-sized team, it is very useful for the team. When you have a higher scale of work, I would say the portfolio management and the reporting need to improve. You either have to build your own solution on the APIs or you have to manage how you can configure in the current flows. My rating out of ten will be seven or eight.

In the next version, I would like to see better reporting and safer plugins, as well as easier scalability.

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.