As a user, my primary use case for JIRA Portfolio is mainly around project management, portfolio management, budget planning, and ideation. It is IT projects specifically related to the oil and gas domain.

Originally, we used JIRA for help desk ticketing, but the biggest use case for the solution now tends to be supporting Kanban and scrum-based agile development.

We use Jira Portfolio in our organization for issue tracking and task management. We had many projects. We didn't use it much for forecasting, but we did use it a bit for release planning by assigning tasks to releases. We didn't use it for project management or scenario planning; we just used it for tasks.

Our organization uses the solution in scrum meetings and cycles for the internal teams. JIRA Portfolio is also used for tracking stories, and roadmap planning. In our company, I am also working on JIRA administration to configure the entire cycle of the stories and Epics by adding customized fields and workflows.

I have used JIRA Portfolio to adjust and add flexibility to the workflows according to the team's input in our organization regarding their working process. 

I started using JIRA Portfolio for development. Typically, it was useful for backtracking in the first place and later for project planning. I tried to use it to track every kind of issue.

We use the solution for large-scale agile planning in our organization and ensure that every project aspect is properly accounted for, like individual products, logged correctly, and progress tracked through the portfolio dashboard. The scenario planning feature impacted your strategic decision-making.

I use this data for resource allocation, called corrective measures or actions where you can take corrective measures beyond reporting. I also use this for backlog grooming and tracking progress.

The primary use case is project management. 

JIRA Portfolio gets used by my company's customers for its capabilities, like portfolio management, project management, and generating high-level project reviews for their CXOs.

We use the tool to track issues and develop pipelines. We also use it for versatile projects in the IT department. It helps to track KPIs, present progress to the business with dashboards, and complete the QA team's plans.

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.

Everyone mentions tasks using JIRA. It is used for various everyday tasks, including dashboards, sprints, backlogs, and workloads.

We use the solution for software development management. It includes the timeline and the requirement definition.

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. 

We use it for ticketing and project planning, and documentation, mainly for ticketing, department-wise ticketing, for the creation.

We are using JIRA Portfolio life cycle management.

The solution can be deployed on the cloud and on-premise. However, most clients choose cloud deployment. Not all of our clients have their own database.

We use JIRA Portfolio to implement the scaled agile methodology and conduct retrospectives. It's also used by us for writing bugs and managing our daily structure.

I use the solution in cases when I need to report something such as escalating a scale. 

We use the solution for tracking stories or issues. Developers create tickets, and project managers track everything using Jira.

Advanced Roadmaps is part of Jira's premium cloud subscription, so it's bundled with the product on the cloud. They've recently included it with Data Center and they've sunsetted the server product. As of today, you couldn't go out and just run the self-hosted product with a server license. They stopped sales of those and support for those.

Jira's got a family of three products. Jira software, which is used by mostly engineering team teams or software development teams. Then they have a help desk solution called Jira Service Management, which is used primarily by IT support folks. They can take in requests. Now, with the advent of Enterprise Service Management, you're seeing more help-type projects for folks. And then Work Management, the last of the three. Usually, most business teams work out of that. You might have marketing teams as well. They don't need all the software features. As a part of the premium package, you get a planning environment, which enables you to plan across projects, not just at the project level in what was formally called Portfolio for Jira. That's now called Advanced Roadmaps. They rebranded it a year or two ago to Advanced Roadmaps. It used to be sold separately. You'd get it as a separate cost and you would install it. It's plug-and-play. It would work on top of everything you already had. Since it was their own product, Atlassian decided to bundle it with the premium tier rather than having every tier including it.

I mainly use Portfolio for integrating systems, such as web pages for different brands. We also use it for loyalty and analytics applications.

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 just use JIRA Portfolio, which is available on the server.

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.

JIRA Portfolio is one of the best tools for storage management. We use it in our data center.

I'm a product manager, so I create entries covered for two products that are developed by the engineering team.

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.

We use JIRA Portfolio for program management for agile team development across multiple product pipelines.

I am using JIRA Portfolio for tracking and reporting issues. We use it for the entire sprint and will have all the information there, such as testing, and all the developers.

JIRA Portfolio is a tool that is primarily used for software development. Our scrum teams and product owners utilize it to manage the software development process. We have an extensive internal software development process that is supported by JIRA Portfolio.

The solution is deployed on JIRA's Atlassian Cloud.

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

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.

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 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 use Portfolio for project planning.

We are using JIRA Portfolio for business estimates and you can attract your product in a very well manner.

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.

We use JIRA Portfolio for management. It handles all our stories and we use the dashboards and reports. We are not fully utilizing all the features, and we use Tableau on top of it for our portfolio-level dashboards.

I am a software developer and we use this product for end-to-end SDLC. It begins with the requirements gathering, then continues with tracking features and planning our sprints. We also use it for tracking bugs.

We primarily use this program as backlog management using Kanban and Scrum and also to model service tickets.

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.

Our primary use for this solution is issue tracking and planning.

The primary use case for this solution is to manage the work that has to be done, everything else is on a repository that is maintained by another tool.

It's how the work has been designed at the beginning of the project. We have one repository where we store all of the requirements, the testing, and all of the activity trackings are done in JIRA.

The deployment model was on-premises.

We work in a development environment so there are multiple changes regarding development on the software platform daily. For each change, there may be some issues and some enhancements. A JIRA ticket is created and published with other procedures that can be handled.

We are using this solution to manage an agile project. We are putting JIRA on our backlog, and we are following the work in progress with the Kanban board. 

We have generated a lot of dashboard in-reporting with JIRA Portfolio to monitor the performance of our direction and our projects team. We have a license for 250 users, and we are going to get a license for 500 users. 

Our primary use case is to establish agile teams and Release Mgmnt process. Jira was implemented, and also Portfolio but each team manages the app as they wanted. The tool is very open, which leads to a lot of error, confusion, and end problems. Then we set up a rule to manage it, based on best practices but if someone made an error therewas no way to avoid it. It is important to have a clear methodology from the company prior to start to use a tool like Jira.

We use JIRA for project management.

We primarily use the solution for issue management.

Currently, we use the on-premises deployment model but we are moving to the cloud. Amazon is part of it but we are in the evaluation part. Our primary use case is for workflow and regression testing. 

Our primary use case of this solution is for organizing our projects and as a tracking solution for our software projects.

We are in a very large company and I am an Agile Coach in our department.

My primary use case for Jira Portfolio is mainly resourcing capacity managements.

This is an ITSA product. We use it to track business flow. The directors and managers assign tasks to us using Jira. It shows us where our customers are at and their status. I'm a solution architect and DevOps engineer.

We use JIRA Portfolio to manage our program of work.