The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area. If you look at the videos they publish on YouTube, other platforms, and internally, they support their users pretty well.

The most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin. 

The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it.

Portfolio's best features are performance and elastic memory.

The entire features that are required for managing the product's communication between the team there are valuable. Managing product development and managing inter-team communications are also valuable features.

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. 

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.

The most valuable features of the solution for my customers are the product's ability to generate dependency reports and provide the basic view where they evaluate the task status, like to which team it got assigned with respect to certain versions and how they are placed.

In general, the valuable features of the tool are its capabilities concerning dependency reports and task status.

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. 

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.

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.

The ability to move across various stages from solution discovery to completion is valuable. We can assign specific tasks to users. We can also see the timeline and the progress of the projects. It makes our work easy and efficient. The tool helps us achieve more within the stipulated timeline and budget.

The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful. 

And I've even worked with multiple analysts, like, for services, and I work on Jira. 

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

Version management is the most valuable feature of JIRA Portfolio.

We can track the open stories or open issues that are there. That's the most valuable feature that I find.

The solution is stable and reliable.

It's scalable and allows for various configurations. 

The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone.

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

Mostly there are two kinds of thought processes. A lot of people are still transitioning from waterfall. They really want the kind of Gantt chart view of the data. That's what's referred to as the roadmap in Advanced Roadmaps.

The other thing that's popular and implemented is the dependencies. Having an option to view dependencies between projects and teams is great. You might have to work to resolve those, remove those kinds of dependencies, or just be aware of them that they exist and coordinate the work between teams. Those two features are the main things. They like the Gantt chart views and also like seeing the dependencies on the dependency port and being able to forge those relationships in that environment too.

The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability.

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 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.

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

The best feature for us is that it is a centralized database. Everyone has access to it. It is a single source of tools. We no longer have to clumsily copy and reconcile Excel spreadsheets.

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. 

The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs. Additionally, its widespread familiarity makes it easier to onboard new employees, and its associated software development tools are a major plus.

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.

It is difficult to narrow it down to features. It's one solution as a whole and to point out certain features is complicated.

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

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.

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.

This solution is easy to use with good analysis integration capabilities with other products. Jira has a wide range of functions. 

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 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.

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.

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.

The dashboard is the most valuable feature. The user experience is very good, it's easy to use.

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. 

The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good.

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.

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).

The integration is very good. We've more or less integrated with everything including reporting and registering. 

The configuration is excellent. The solution allows for the possibility to configure to your specifications. You can define projects separately, for example. If you want to configure anything, even to do a dashboard for a specific project, or user, or to define rights, etc., you can.

It's hard to say which one feature is the most important. There are many we find extremely useful.

The most valuable feature of JIRA Portfolio is the visuals it provides rather than Kanban boarded tickets.

We use all of the features. The most valuable features are the reporting of the speed of the team's progress and the long-term organization of our projects in the timeline. 

All of the charts, including the Burndown chart, are very useful for us.

The graphics and the resolution of the work are very good.

The JIRA command line is also a very valuable feature.