JIRA Portfolio Reviews

The solution is simple to use. We use JIRA Portfolio with Azure Logic Apps, and it is easy to integrate them.

The solution should provide a monitoring interface for the customers to have more information about the issues. We cannot receive the information by mail. We can use the tool to share reports, but it should also have a space for customers to add comments. JIRA should provide more online video resources explaining how to use the solution.

I have been using JIRA Portfolio for one year.

I rate the solution’s stability an eight out of ten.

Overall, I rate the solution a seven out of ten.

We sometimes use JIRA Portfolio as an agile solution. Sometimes, we use it as a kanban solution. It was all dictated by the type of work that each team does.

The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work. As new work was identified, we could properly slot it in, schedule it, and manage it. This visibility helped us increase the confidence in delivery and launching and decreased the variance to the planned launch date.

The solution’s pricing could be reduced.

I have been using JIRA Portfolio for 20 years.

I've used the solution both on-premises and cloud, and I've never had any performance issues.

I rate the solution ten out of ten for stability.

I've never had any issues with the solution's scalability or availability.

I rate the solution’s scalability ten out of ten.

If you do not understand the environment, the deployment will not be easy. Since I have used JIRA for quite some time and understand the Atlassian ecosystem, the initial setup of the solution was very straightforward for me.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution’s initial setup an eight out of ten.

Given the solution’s significant functionality, benefits, and value, you get more than you pay for.

I used the solution's Advanced Roadmaps feature instead of the regular roadmap feature. I liked it because it provided a visual that allowed my leadership and my partners to understand the roadmap, when we were getting work done, and when we were launching a feature or functionality.

I've mostly found solutions when I go to the community. I google JQL a lot, which is probably the extent of my interaction with a community knowledge base.

JIRA Portfolio helps facilitate cross-team collaboration in projects. In Jira, you can explicitly define a dependency between work, issues, and items within different projects. With Advanced Roadmaps, you can create initiatives and projects that facilitate cross-team collaboration in projects.

I would recommend JIRA Portfolio to other users because it provides good visibility. Jira gives you the tools to see what work you've planned and if there are any dependencies or risks that might be creating any issues.

The solution has adopted SAFe, which is a type of process management, workflow management, and software. The Advanced Roadmaps is the type of tool that helps support SAFe methodologies, which are an extension of agile project management.

Overall, I rate the solution ten out of ten.

We use JIRA Portfolio for project management and delivery. We follow a Kanban board for new tasks, schedules, releases, bugs, and enhancements. Every new project is onboarded on JIRA Portfolio.

JIRA Portfolio is easy-to-use and has a lot of data we can track easily. The solution has good reporting and is very user-friendly. The developers can pick it up easily, and the solution's collaboration is very nice. It helps resolve a lot of collaboration issues, requirement issues, and also the metrics part. We can track the metrics straightforwardly and then see where we stand and what needs to be done.

It would be really nice if the solution provided a heads-up every time they enhance something or add new features. Recently, we had an issue because they changed the structure of using demo accounts. We didn't have any heads up and were struggling with what to do and how to go about it. We had to reach out to a lot of people, ask if they were also facing the same issue, and then we finally had to figure it out ourselves.

JIRA Portfolio is an amazing tool, but it would be much simpler if it provided a heads-up about how to go about new changes beforehand. The documentation for these changes is available online, but it's too much. If the solution comes up with a change, it should only provide information for that particular change. Otherwise, we'll have to spend a lot of time looking into a lot of documentation.

I have been working with JIRA Portfolio for four years on a continuous basis.

JIRA Portfolio is a stable solution. We've not come across bugs in the solution.

JIRA Portfolio is a scalable solution with no storage, user, or project issues. Around 18 users are using the solution in our organization.

Initially, when we had to configure the solution, we contacted its technical support team, which is well organized.

Before JIRA Portfolio, we used Microsoft Project, which was messy and painful with its Excel sheets.

The best thing about JIRO Portfolio is that its initial setup is very easy. You can start a Kanban board in a couple of minutes and then start communicating and adding users.

Our organization has seen a return on investment with JIRA Portfolio regarding the ease and the issues in managing the project or program, collaborative and documentation issues, and requirement issues. With JIRA Portfolio, there's improvement in the processes, the execution, and the delivery time.

We use a cloud version of the JIRA Portfolio.

My suggestion would be to come up with a customization plan or a business case regarding what you need for a particular project and what is possible and what is not possible with JIRA Portfolio. Then, present that business case to the technical team to avoid issues later.

I've seen scenarios where we didn't put forth a particular question and had to reconfigure and move everything to a new project. It's best to understand the project requirements and then configure accordingly to avoid such a situation.

Overall, I rate JIRA Portfolio a nine out of ten.

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.

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. 

I use the solution in my company for project management, especially when we have agile projects. My company has used the tool for planning, tracking, and action.

I have had little exposure to the tool, so I cannot speak about what needs improvement. I have used the product on a very minimal basis.

As there are no perfect solutions and considering that I rate JIRA Portfolio's stability an eight out of ten, I feel it is an area with certain shortcomings where improvements are required.

I have experience with JIRA Portfolio. I have not used it very actively. I use the tool on and off.

Based on my limited exposure to the product, I rate the tool's stability an eight out of ten. I haven't faced any problems with the product's stability.

It is a good scalable solution that I have used for small projects and reasonably large projects.

In my organization, there are teams consisting of 15 to 20 members who use the product.

I have not used any other solutions in the past for purposes similar to what I currently use JIRA Portfolio for in my company.

The product's initial setup phase was pretty okay, so it was not too bad.

In terms of the product's ability to improve the productivity of teams in our company, I would say that we have found it useful when we have to deal with projects, specifically agile projects, where it served to be very useful because it was directly applicable for planning and tracking.

I recommend the product to those who plan to use it since it is a useful solution. For my company's work, the solution had all the features we wanted, which is why we were happy with it.

The benefits associated with the use of JIRA Portfolio revolves around the fact that it is a good project management tool for our company, as it was helpful in managing our project activities.

I rate the product a nine out of ten.

JIRA Portfolio is used in our organization for scrum projects. The solution helps manage projects, plan sprints, and execute the planned sprints. The development team is the major user of JIRA Portfolio in our company. 

The solution is sometimes complex to use, especially when Confluence is used along with JIRA Portfolio. 

I have been using JIRA Portfolio for nearly 15 years. 

The solution is stable enough. I would rate the stability a ten out of ten. 

The solution is highly scalable and flexible as well. Even without availing of add-ons from the vendor, the basic JIRA Portfolio is enough to make customizations according to the use cases or projects. I would rate the scalability a ten out of ten. 

Until now, at our company, we never had the need to seek customer support because we never faced any issues, downtime, or server porting with the solution. 

The initial setup of JIRA Portfolio is quite straightforward. I would rate the initial setup an eight out of ten. As it's a cloud version, the solution setup process is very fast; you just need to create an account and mostly provide access to team members.

In most cases, one professional is enough to deploy JIRA Portfolio. I have witnessed the solution being used by small, medium, and enterprise-level companies. The setup process majorly involves getting access to the JIRA cloud and the subscription. 

The solution is offered at a high cost and the price further escalates depending on the number of add-ons availed. The solution is very popular and a huge number of companies are using it, so I believe the product is not unaffordable. 

JIRA Portfolio is used to track time in our company. For reporting purposes in our organization, we use Power BI, and JIRA is integrated with Power BI for all tracking needs. 

The solution helps you organize projects and it can be complex to use, especially when Confluence is used in integration with JIRA Portfolio. How someone utilizes the flexibility of JIRA Portfolio's issues, epics and stories depends upon the individual's interpretation of the solution.

The solution is worth its price to keep you on track with projects. Whether the tool gets used in the Kanban or Scrum method depends upon the development style at Agile. JIRA Portfolio is mostly used for Scrum because there are sprints available, projects can be planned from a project management perspective, ABCs can be planned, dates can be fixed and it seems more organized than other methods. 

The solution is also used in Scrum because the management, future releases and roadmaps can be planned. There are similar project management tools. I am aware that a similar tool like JIRA Portfolio is hosted by Azure, especially for developer teams, but I would still recommend JIRA Portfolio if it seems affordable to the company or professionals. I would overall rate JIRA Portfolio a nine out of ten.  

I just use JIRA Portfolio, which is available on the server.

When I develop software, there are many things and we need to check the status. Then, I use JIRA Portfolio in all areas, such as JIRA's use for tracking software issues from QAT. When we needed to check the plan of our project and manage the project status, I usually used JIRA. And if there is some field issue or customer service field issue, we gather the field issues using JIRA.

I think the solution's most important and valuable feature is its ability to track the issues. We can also check the status using JIRA, which is a good function in the solution.

Our major team does not control or manage JIRA server well since sometimes there is trouble using the solution, which is a problem. The solution's speed needs to be improved.

In the future, adding certain functions should be made easier in JIRA.

I have been using JIRA Portfolio for around ten years. I am a software developer who uses the solution. Also, I don't remember the version of the solution I am using.

I rate the solution's stability an eight out of ten.

I rate the solution's scalability a nine out of ten. It is a very scalable solution. Around 2,000 people are using the solution. In my lab, 10,000 people are using the solution.

In the future, we may change to an ARM system.

I haven't contacted customer support yet. For doubts, I talk with my infrastructure team. I think JIRA's tech support is good. I rate the solution's technical support an eight out of ten.

Positive

Previously, I didn't use a different system. I just opted for Jira.

The initial setup is easy. I rate it a nine on a scale of one to ten, where one is a difficult setup, and ten is an easy setup.

I can't comment on the time taken for deployment since I don't manage JIRA server.

Maybe there are some people who manage the server using JIRA application. I guess three people are managing the solution.

A set of people were involved in the deployment of the solution.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing an eight. There is an additional cost to be paid for some kinds of tools.

I recommend the solution to those planning to use it. I rate the overall solution a nine out of ten.