JIRA Portfolio Reviews

We use Jira to manage the software development lifecycle. We create a project in Jira and capture the requirements at various levels, including epics, features, objectives, stories, defects, etc. One hierarchy can have multiple levels that can be linked, so requirements are more traceable.

Jira's Structure, agile, and Kanban boards are helpful. I also like JQuery, which allows you to fetch the relevant set of data. We use JQuery, JQL, and the Structure board a lot. Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts. 

Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights. 

I would also like if Jira had a centralized space for accessing project-specific documents. Furthermore, they could enhance the graphs and charts to make them more presentable.

We've been using Jira for around nine years.

Jira's code is excellent. I can quite export using Jira and smoothly use any of its features or link it with other tools to build a chart. I often use Confluence to depict our team's progress on a project. 

Scalability is one of Jira's main advantages. When demand increases and an organization needs more space, Jira can support it. It provides several add-ons and connectors to link to Jira with other tools like Confluence, Excel, or various other options. We have more than 1,000 people using it.

I have never had issues using Jira, so I've never contacted support. 

Setting up Jira is straightforward. 

I believe we pay a monthly license for Jira, but I don't know the precise cost. I think it's dependent on how much space the organization uses. The vendor may offer a range of pricing options based on the organization's requirements. 

Jira is the standard across the globe. This is the market leader for maintaining or managing software development, and it has cost advantages over other available tools. 

I rate Jira Portfolio nine out of 10. Jira is the best tool in the market, but it still has room for improvement. At the same time, it's pretty easy to understand. There is a lot of documentation and videos online, so anyone can quickly learn various features.  

I recommend Jira Portfolio for big organizations that want to maintain the software requirements. Jira's cost may be too high for smaller organizations, but several cheaper options are available. 

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.

I primarily use the product to collaborate with the product and engineering teams. Depending on the product stage, I may draft or review the PRD, providing feedback for improvement. I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely. 

Before, I used Excel, but switching to this tool has been a significant improvement. It's much more collaborative and user-friendly. With many functions, entering and processing data is easier and faster. I can easily link documents to clients and perform tasks like inserting tables with simple commands, which helps speed up my work.

Jira Portfolio is part of our standard operating procedures to ensure product functions run seamlessly and smoothly. Providing people with sufficient tools to collaborate effectively is crucial to achieve this. Jira has become the go-to document processing tool for facilitating this collaboration and ensuring productivity. Every aspect of the product is critical for your workflow, whether gathering input from team members or seamlessly writing and managing documents.

We are based in India; I would like the product to integrate local pricing. We earn in rupees but spend in dollars. Its pricing could also be lowered. 

I have been using the product for three and a half years. 

I haven't encountered any stability issues. 

I haven't contacted the technical support team personally. 

Jira Portfolio's deployment is easy. We started by signing up for the software's seven-day free trial using our credit card.  After the trial, we decided to opt for a paid plan based on the number of licenses we needed. As for any custom plans or requirements, we haven't reached that scale yet, but we know we can contact their team for further discussions when needed.

Integrating Jira Portfolio with Slack, Camunda, and other tools is part of our standard operating procedure. It helps in coordination. However, I didn't handle the integration myself. Instead, I relied on a team of more experts about the product. 

Our team has worked with the product previously and didn't need to overcome learning curve challenges. 80 percent of my organization is well versed in it. They can help people who don't know the product. I rate it an eight out of ten.

We are currently testing this solution with our primary use case being to deal with certain types of projects such as Cascade and Agile, as well as others that involve moving to a ticketing service, basically everything related to project management. I'm a project office supervisor. We are users of Portfolio. 

I like this solution because it has many functionalities. I love the supervision and the workflows that we can use for making a flow inside Jira. I love too, that we can take control of GitHub as it relates to project flow. Portfolio provides a good service that gives control over ticketing and control over the versions of the product. It provides resource management related to our projects.

This solution requires some effort to insert functionalities from Tempo to the base of Jira. I think that could be simplified.

I've been using this solution for three months. 

This is a solid solution and very stable. 

Portfolio is very easy to scale. 

For enterprise companies the licensing cost is fine. Those companies don't have budgetary issues. It's mid to smaller-size organizations like us that find this tool very expensive.

If you have the budget, then Jira is the way to go. 

I rate this solution nine out of 10.  

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.