Mechanical Engineer at a educational organization with 501-1,000 employees
Real User
Top 20
2024-02-08T10:30:56Z
Feb 8, 2024
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 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.
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.
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.
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.
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.
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.
Principal Solution Architect at Trundl - Atlassian Platinum Solution Partner
Consultant
Top 10
2022-07-18T07:38:57Z
Jul 18, 2022
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.
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.
Line Technical Agent at a comms service provider with 1,001-5,000 employees
Real User
2020-08-16T08:00:00Z
Aug 16, 2020
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.
Software Developer at a manufacturing company with 5,001-10,000 employees
Real User
2020-08-09T07:19:55Z
Aug 9, 2020
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.
Senior Management Consultant at a consultancy with 11-50 employees
Real User
2020-07-27T18:56:00Z
Jul 27, 2020
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.
Technical Manager at a tech services company with 1,001-5,000 employees
Real User
2019-11-13T05:29:00Z
Nov 13, 2019
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.
Test Manager at a financial services firm with 11-50 employees
Real User
2019-09-24T05:43:00Z
Sep 24, 2019
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.
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.
Jira Portfolio is an agile roadmapping tool designed to help teams build plans, envision the big picture, track progress, and share the process with stakeholders.
Jira Portfolio is planned based. A plan in Portfolio is a complete view of the tasks, teams, and release dates for your Jira projects. Once you start to create a plan, there are three main factors you need to define:
Scope: A list of tasks that need to be carried out in order to complete the plan.
Teams: Who will be...
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 use the solution for software development management. It includes the timeline and the requirement definition.
We use it for ticketing and project planning, and documentation, mainly for ticketing, department-wise ticketing, for the creation.
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.
We use JIRA Portfolio for program management for agile team development across multiple product pipelines.
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.
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.
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.
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.
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 use the solution for tracking stories or issues. Developers create tickets, and project managers track everything using Jira.
I use Portfolio for project planning.
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.
We are using JIRA Portfolio for business estimates and you can attract your product in a very well manner.
JIRA Portfolio is used by our product teams to collaborate on projects,
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.
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.
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.
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.
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.
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.
We primarily use this program as backlog management using Kanban and Scrum and also to model service tickets.
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.
Our primary use for this solution is issue tracking and planning.