JIRA Portfolio was a much more appropriate solution to support our move to agile systems development and implementation.

The solution has improved our production process. We have fewer issues and everything that happens in our process is captured in the solution.

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

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.

As a project management team, we’re supposed to manage the teams that develop different products. It can be hectic if we don't have a tool. With JIRA, it's very easy and seamless. All the teams can give their updates, check on their backlogs, and work on them.

This product has helped our organization by allowing us to stop using Excel. We now have one team source as a centralized database. We no longer have to reconcile data or deal with differences in multiple sources.

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. 

There hasn't been an improvement because we were using JIRA solutions before.

The solution has improved our function level because we have a clear view of everything. 

We were able to implement the Kanban and Scrum methods using JIRA. That was a really good argument. We had been using the waterfall method, so this really helped us to get that out there to our general way of working.

It was very easy to load tasks, assign responsibility, due dates, etc. Also, it is easy to make follow-ups. The problem is that there is not a log to track how many times the same issue was created or how many times the issue changed the due date. This is a problem when you want to improve the way of work of your team. 

Additionally, with Jira Portfolio, we had the possibility to track all the projects in the old way with some gannets but you need to be very careful with the filters. One wrong filter and the data is totally invalid

Since we have been using JIRA Portfolio it has improved our productivity and visibility.

It allows me to do the capacity management and it allows me to qualify my ethics, and that's what the capabilities I was searching for in a solution like Jira Portfolio.

Before JIRA, we used to organize our software with Bitbucket but now, with JIRA, it is more efficient to organize all the work in the timeline, make long-term plans for one or two months, know what our deadlines are, and write short summaries in the backlog. The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized.