JIRA Portfolio Reviews

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 are using JIRA Portfolio for business estimates and you can attract your product in a very well manner.

The most valuable feature of the JIRA Portfolio is the many features it provides, such as code integration, documentation, roadmap, and Eclipse. The solution is useful for product managers.

JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools.

In a future release of JIRA Portfolio, they should add more general features to make it easier for project management.

I have been using JIRA Portfolio for approximately eight years.

JIRA Portfolio is a stable solution because it is on the cloud and it is one of the main reasons we chose it.

The scalability of the JIRA Portfolio is good. If you want to add more users you will only need to purchase the ability to have more users.

We have approximately 50 people using its solution in my organization. The users consist of managers, field workers, operational managers, and other teams. Everyone from junior to senior level is using it.

I have not needed to use the support.

The initial setup of the JIRA Portfolio is in the medium range of difficulty. We needed some training to be provided to our teammates. However, after the training, we were more capable. Without the training, we could not access very much or assign any product.

The setup of the JIRA Portfolio is continuous, it has taken us eight years.

We have a license to use JIRA Portfolio, we are not using the free version.

We needed complete visualization for our product which JIRA Portfolio was very capable of. As a product tracking tool, it was very good.

Whether or not this solution will be a benefit to your project depends on a lot of factors, such as your requirement.

I rate JIRA Portfolio a nine out of ten.

JIRA Portfolio is used by our product teams to collaborate on projects,

Portfolio's most valuable features are that it's user-friendly and customer-centric.

The price could be improved.

I've been using this solution for a year.

Portfolio is stable.

Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support.

The initial setup was difficult because we had issues getting a direct channel. It took around two to three months to deploy.

We used an in-house team to implement.

I would give Portfolio a rating of 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.

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.

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.  

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.