JIRA Portfolio Reviews

We use the solution to create a unified roadmap that allows us to track investments and actuals. Additionally, we need a single view that displays the work items assigned to each value stream, and we need to prioritize these items according to the WSA technique.

The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects.

The reporting has room for improvement. We were working on a project, trying to figure out what our task was and when the start and end dates were. This wasn't too difficult, as we had all the information we required, however, we had to align a lot of data in order to get the right information, which was a bit of a hassle.

The initial setup could be more user-friendly. Additionally, it's important to consider portfolio-level metrics. Having more portfolio-level metrics would be beneficial.

With Jira, an issue that arises is the length of time it takes to show certain data. If this could be sped up, the user experience would undoubtedly be improved.

I have been using the solution for one year.

We have some issues with the stability.

The solution is somewhat scalable.

Tech support can be reassuring but requires some effort to get the answers we need. We have to search through conference pages to find solutions, which may take some time, but we can purchase a service that provides ongoing support.

The initial setup is not straightforward. 

We don't take a big-bang approach. We start by deploying one piece of art and then presenting it to the leadership. They need to have an overall view of how it's progressing. If all the necessary data is available, it may not take more than two weeks to implement.

To properly implement, it was important to first tag the teams and their respective tasks and to assign them to the relevant ethics. Additionally, it was also important to set deadlines for the completion of the tasks. One of the biggest challenges is people not putting in their estimates, which hinders accurate tracking of progress.

I give the solution a seven out of ten.

We have one person per year using the solution.

I use the solution in cases when I need to report something such as escalating a scale. 

The solution includes good and fast notifications for other project team members. 

The solution's look and feel could be a bit more intuitive and user friendly. 

I have been using the solution for one year. 

The stability is rated an eight out of ten. 

The scalability is rated a seven out of ten. 

The technical support is good so is rated a nine out of ten. 

Positive

It is important to learn about the solution's functionalities and features to prepare for use. 

I rate the solution an eight out of ten. 

I use Portfolio for project planning.

Portfolio's best feature is integration with other JIRA products.

In the next release, Portfolio should include more metrics and develop their portfolio planning.

I've been using Portfolio for several years.

We've had no issues with Portfolio's stability.

Portfolio is scalable.

I haven't used JIRA's technical support personally, but I've heard from others that it's good.

The initial setup is straightforward.

We used an in-house team.

Portfolio is very expensive, costing on average $2000-3000 per user per month. 

I would rate Portfolio eight out of ten.

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. 

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.

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

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

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

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. 

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

There were a few colleagues that handled the initial implementation. 

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

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

I would rate the solution eight out of ten.

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.

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.

The HR aspect of the solution could be improved. 

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

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

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. 

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

Positive

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. 

I do not have any knowledge of the licensing cost.

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.

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.

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.