JIRA Portfolio pros and cons

Having an option to view dependencies between projects and teams is great.

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.

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.

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.

Its stability is very reliable.

We have found the solution to be stable.

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

The initial setup is simple.

Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company.

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.

It's got kind of a steep learning curve.

Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.

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.

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

It would be nice if it could provide an end-to-end solution for a project.

The HR aspect of the solution could be improved.

We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version.

If you want to generate a report for individual usage, it's difficult.

An improvement would be if Portfolio were integrated with Office 365.

The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client.