What is your primary use case for Jira?

The solution is used for project management and agile software development. It is also used for general business planning. We can use it for any small or large project. The tool is designed to do sprints and Kanban. It was built for Agile. It works well for any Agile-style project.

We use Jira for project management and tracking.

We are using Jira to plan and manage projects, including tasks, sprints, and releases. It allows teams to create, assign, and track issues. It supports various agile methodologies like Scrum and Kanban, providing tools for backlog management, sprint planning, and burndown charts. It offers robust reporting capabilities, allowing teams to track progress, monitor team performance, and generate visual reports. Jira's user-specific dashboards and reporting capabilities provided insights into individual and team performance. This promoted accountability and allowed our development team to recognize and reward high-performing team members.

Jira is used for all the project management, on all the stages of project management. So then we create a Kanban board and move on to creating the stories. We create the story points, break down the requirements, and then create the Sprint accordingly. Based on that, we can manage in Jira how many user stories we will pick in what Sprint. And based on the dependencies of the user stories, this is the flexibility that Jira provides. Then we have also got various, you know, sub-tasks, which we have to complete to accomplish the DoD (Definition of Done). We can mark the Sprint as complete when these particular tasks are completed. So that gives very good monitoring of the project where the project is going on. When it comes to the testing part, so testing is end-to-end on Jira. We can take the user stories based on the acceptance criteria. The test cases are created in Jira, and the business analyst team reviews those test cases. Based on their feedback, the test cases are updated. Those test cases are being executed. So there is clear tracking of the test execution, and all the test cases are also linked with the user storage. We have end-to-end tracking of what test case is executed for what user story. So that is the best part of Jira.

We use it for project tracking. We do software development. We implement software development lifecycle, and we use Bitbucket for CI/CD pipelines.

We are using it for software development tracking, bug tracking, feature tracking, and so on. We are using the cloud version from Atlassian, and we have its latest version.

We use Jira for project management.

We are using Jira for the internal project and issue management or tracking.

We are using Jira for our test management. We're using it to record our inspecting results and to regulate the evidence in the report.

We use Jira to manage agile development from beginning to end. First of all, we lay out a backlog of everything that needs to be done. Within the backlog, We define a sprint of three to four weeks and prioritize in Jira. The backlog is stored and the sprints are defined in Jira. The tasks or stories fall under the umbrella label "issues." The issues are created and assigned to developers, and the testing is tracked in Jira. After one is done, it moves into the QA stage. We track that all the way until we get to what is called "non-performance testing," which is part of production. We use Jira to track the status throughout, and we have daily stand-up meetings where all the developers get together to talk about their blockers, interdependencies, the net, etc. All of this is captured in Jira. Our client is a bank, and we use a cloud version of Jira. We are the supplier, so we're onboarded and get a login for whatever they're using. Right now it's a cloud version that we are signed onto. They use a hybrid cloud because they have their own cloud because some of their systems are private, and some are in the public cloud. The bank works with a few cloud providers. They are using Google for this project. We are heavy into developing microservices, which use JKE, Google layer, Google Cloud Platform, Google Communities Engine, and all the other Google components for microservices development. Most of their stuff is deployed on Google, but they are also affiliated with a bigger bank that uses Azure, so some of their systems are deployed on Azure.

Jira is used for issue tracking and defining the development pipeline. It's helpful to define when a project is done and track a task as it moves through different stages. The deployment type varies based on the customer's environment. We sometimes connect to the client's setup, which can be in the cloud or on-premise.

I use Jira for user stories, tasks, bugs, track releases, track backlogs issues, burndown, and test reports.

We are using Jira for task management.

We use Jira for software development and issue tracking, enhancement requests, and software lifecycle management.

We use Jira strategic management and overall best practices management.

We use it for project and sprint planning and day-to-day bugs. We also use it for documentation, engineering, and enhancements tickets and for creating the feeds, which are like new features. We are most probably using its most recent version.

We use it within our organization. It's to handle all the main technology projects. It's for managing mobile banking, internet banking, all the new products, and all technology-related projects.

My organization primarily uses Jira for project execution like managing the sprints, sprint planning, task creation and execution of the project on a sprint basis. They also use Jira for other insights into how our team is performing and the velocity of the team. They look at the dashboard and report to see how are we delivering minimum viable products (MVPs) on time.

Some of the use cases are for tracking issues and bugs. I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan. The solution is deployed on-premises.

Our organization is a software development company. We serve financial institutes that have between 8,000 and 13,000 employees. We use Jira for process automation and as a workflow engine on the client's side. For example, a customer can fill out a form and ask a question, which is operated by Jira, and someone will be prompted to contact you with the answer. We created the forms designer and the roof engine and handle the process with the customer contact. We are using Jira for automatic tools, so it is run on-premise.

I use Jira for the development of different versions of software, upgrading it from one version to another, and developing and collecting specs for the new versions.

I use it for portfolio countdown. I work as an enterprise architect in the company, and my usage of Jira is minimal. Software engineers in our company use Jira very heavily, but I do not use it for my day-to-day work.

The primary use cases for this solution are backlog management and sprint planning. Customers deploy this solution on-premises.

We are using Jira Interview to handle all the facts from clients and schedule calls with them. We have a different operations department that configures Jira, and we have technical people that help us choose the deployment model. The main reason we are using Jira at this time is for a different dashboard and chart. The major one that we are using is for the stock analysis, and it's nice to get that time log for our team, get the score of the game, 40 points delivered in a week or a month. we are using Jira for following purposes: Issue tracking Customizable workflows Estimation & work logging Progress reporting Scrum boards Kanban boards Project-level permissions Project backlogs Email notifications Roadmaps

We primarily use the solution for our own projects.

We use Jira to create releases, tasks, sprints, and collaborate within teams. The solution can be deployed on both the cloud or on-premise.

We had a regulatory requirement through our legislature to collect motor or voter information for residents of California. So, if you basically wanted to sign up to vote, you could do so at a department of motor vehicles. The Jira instance was used for what we call the new motor voter, which is the online premise to register to vote when you conducted a DMV transaction, such as vehicle registration, driver's license, renewal, etc. We had its latest version. It is online. In the cloud, we set up an account for the department, and then add users as needed. It is a government cloud.

I personally use Jira for project management and agile software development. I'm an information technology program manager and we are customers of Jira.

We use this solution to manage our projects.

We are using it for project management.

I am working on a project which involves moving Jira onto the Azure boards. We use Azure DevOps for our repository and pipelines and we are looking to move on to Azure boards from JIRA for our ticketing or change request management.

I am currently using Jira for project management purposes, such as tracking the team and opening tickets. I am an admin in my project. When we start a new project, I open a new story in Jira for that project, and I open sub-tasks for that project. From there, I create backlogs. Our team is responsible for those backlogs. I have previously also used Jira for designing workflows for our enterprise.

We primarily use the solution for project management.

I primarily use the solution for project management.

I work for an insurance company that has developers who need to be tracked. We're working on converting the spreadsheet into a Kanban flow environment. I'm the program manager/master.

We are using the recent version. We use it for story and sprint planning, as well as for reporting.

I believe we are using the latest on-premises version.

We use Jira to manage all our software development projects and our engineering projects. Our main use of the solution is for the workflows on our different types of projects. It's mainly used by our engineering groups, they have the proper workflows and all of the stats. As a director, I work more at the business level, tracking tasks similar to the new planner that's in Microsoft which some people are switching to. We also use it in the backend of the projects. For project managers and directors, it's more about a to-do list thing that's shared. I'm a company director and we are customers of Jira.

I'm overseeing the developments done in Jira.

We using this solution to handling all of our development and support tickets.

I'm working on creating test cases and one test. I also have an overview of the Sprint.

We used it in my previous organization for project management, product management, and release management. In my current organization, where I started working a week ago, we are using Jira strictly for help-desk tickets. We are using DevOps for our release management. So, we've got DevOps, Jira, and some homegrown stuff, and I'm trying to figure out what's going to work best for this new organization. I've used Jira and Confluence previously, and this is my first time using the help-desk ticketing system. It is cool and not a whole lot different than SolarWinds or Zendesk, except the appearance of it is more Jira.

There are so many use cases for Jira. If it's got something to do with IT, it will be covered by Jira. They have a very extensive marketplace and you can find nearly every solution there, including version controlling, source control for the code, automation, test automation, security scanning, configuration, and development management.

We primarily use the solution for customer service and managed services, and for all the workflows for the services. It's also a bit of a CRM. We use it largely for technical support.

We use this solution for project management. It can be used across a team. Managers can assign tasks and then they can track the progress. They can put the start dates, end dates, and everyday comments. They can upload the relevant files to that module. Jira is used to manage a sprint, which is the terminology used in the agile practice of project management. Sprints can be tracked fully using the Jira software. A sprint is typically a part or a subset of the entire work. It has a definite goal. For example, if I am building test software, and building the login page is one module, then I can track the work created from the starting stage to the end. It's a part of an entire software application. If a login page of a website is a subset of an entire website, I can track that right from when it started, how long it takes, what is pending, and how long the control test is. Basically, you can clump it all together as if it is a team and you can measure the speed of the team. It enables the predictability of a project and helps determine when it can go live.

We use one version of Jira internally and we also have another version of Jira that we use externally for our customer. We've been using it for both. Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product.

My people use ASS. I can define spins, I can define roadmaps, I can define components, I can do releases, I can define all kinds of issue types, heartbeats, some of those things. I'm using it for both business and software. In software we have Scrum and Kanban onboard, whereas for business we have the service and then there are those other options. We have multiple use cases. I'm the director of the company.

Our primary use case for Jira is for requests for tracking the software development. We use Jira for the process, especially for password tracking. We're the issue management team for development. We are quite new, so I was very interested in ITSM documentation provided by Jira. But, I needed time to readjust that to our organization as per the line of business. Overall I think it's helpful, but I need some time to absorb all the knowledge.

We mainly use Jira software, including Jira Issue Manager, for bug tracking and project management, and have done so for over a decade. Then in the last six years we have also used Jira Agile in a lot of our project management work. We use the enterprise version of Jira.

We are using the solution for project and defect management, and task tracking.

We primarily use the solution for bug tracking. It's for customer support purposes.

We are using Jira for tracking and management.

We use Jira for the overall issue management in development projects. We use it to maintain a high level during each sprint, which is a requirement. We also use Jira for issue management during testing. We create a test plan and manage it all with Jira.

Right now, I'm just trying the solution out. I'm doing a POC.

We primarily use the solution for product development efforts and documentation. We use Confluence as well for documentation.

I use it for project management and agile scrum projects. I am a manager, and I work with backlog tools and sprint plans. I only use Jira for backlogs, sprint reviews, and data reports. Our project manager is the person who is really working with Jira along with the team. We also have Confluence and Bitbucket. We use CloudBees and DevOps for the deployment of the environment.

It is mostly used for communication, managing requirements, managing defects, and managing stories. We don't communicate much through Outlook. The majority of the work-related issues are assigned to us, or we assign them to developers through this solution. I've been using this solution for managing requirements and defects. I have also been using it for logging user stories and general communication.

Our primary use case is for our own network operations, and integrating via API with our customers network operations teams.

We use Jira product in the organization to automate the software development life cycle.

Virtually every day we have our daily scrum. Our team gathers around the board, which has all the columns showing where the tasks are standing: requested, planning, ready-coding, review, etc. Together, we view one task after the other and update the statuses. It's really a focal point of the team to know where the work stands, and what's the progress of the work since the last time we checked. Within my company, there are roughly 25 employees using this solution. We have a scrum master, who's the most knowledgeable person on the tool. usually, they're the ones organizing the tasks, creating new tasks, and then creating the report at the end of the sprint or the quarter. They're the person who's creating the reports, using the more advanced features. That's the scrum master. There are the developers, including me as a tech lead. There's the tester. There are managers — once in a while we have to present them with some reports and statistics, so they know how much work is being achieved, but they don't have in-depth knowledge of the tool. It's really an internal tool, so the customer is not involved. We're not expanding much at the moment. We've been expanding in the past year, but now things have slowed down a little bit due to COVID-19.

I am the software developer manager and I use Jira to manage team performance. We're also starting to use Jira for our drives. I used Jira before, for creating user stories from boards, to discuss issues, and many other tasks. Today we use Jira, Confluence, and BitBucket in our work. We practice scrum in our organization.

We have a service desk for customers. We have the whole flow from customer feedback throughout, committing with a relation in the code in Bitbucket. We have the tracking and tracing, including all tracking of the issues all the way from the customer throughout the JIRA prioritization in backlogs and sprint planning and connecting those through the actual code commit in BItBucket. It's all done through JIRA to the service desk issue and back again to the customer. The entire ecosystem is quite connected.

We are using Jira to manage our development sprints.

In terms of using Jira, I was more on the user side and not really acting as, for example, service desk or support for the Jira installation. That was not my part of the project. I was more tasked with setting up the infrastructure from the architecture point of view. We needed a ticketing system and we need a planning system and the team that was responsible for the tools was installing and providing them with the workflow that we needed.

We use the solution primarily for project management. We organize our work by projects with epics, et cetera. Below that, I believe we are using a Zephyr plugin for QA. We don't use it for product planning.

We use Jira for software for product development, planning, some hardware product development, and for some solutions and services. Other teams in our company use Jira for scheduling daily work and daily tasks and try to organize or manage products and projects.

We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there. With that, I am able to create a kind of gauge, estimate, and forecast our capacity planning for the next two weeks. We use it to create peer reports.

We are using Jira as our help desk solution, as well as for managing our software development efforts.

I have been the product manager for several years. I use it day in and day out to manage my team. I manage two teams at the moment and they are pretty large teams. Each has a minimum of about 12 people. We use not just agile, we use a scale model framework. All the work is managed through two pieces of software we use. One is called Jira Align. For the portfolio level software, what Jira bought recently, the previous name for the software was AgileCraft. All of the portfolios and features come loaded in Jira Align. From there, they will be composed into stories in Jira. That process is done using programming preventative planning. We do it every three months. All of the stories are tracked. We have a workflow defined and we have statuses defined. As the team works on the story, the story moves from one status to another and we close them when everything gets carried over to the production release.

We use Jira primarily for Agile development and change management.

The primary use case of this solution is to manage work, to distribute work to the teams, and we use confluence as a SharePoint for documents and to use AgileCraft.

I am a consultant, and we have some customers with projects who use Jira. We have customers with different Jira installations because there are so many vendors. It is mostly used as a bug tracking system with tickets, issues and tags.

We use Jira for multiple uses; project management, task management, and we are starting to use it for release management.

Our primary use case for JIRA is for entering user stories into the login books.

The primary use case is for software development teams to manage their work.

We primarily use the solution for project management purposes.

We have a development team and we use Jira to manage our projects. We use several products by Atlassian whenever we create and work on a new project. We have scrum masters who write new project stories, which are tracked by Jira.

We use it to trace our business needs development. We have some nice dashboards out there where we can track needs for clients or track internal projects.

We have various use cases for it, one being for object storage. It's a government entity so that's what they use.

We use Jira to manage scrum projects for the different projects in our company. Our business is a development company that uses the cloud version of Jira to manage the sprint and releases for each project for each client. We manage scrum and cascade projects with our clients.

I use this solution for general issue management, software planning, and change management.

We use JIRA for software development projects and the implementation of business workflows. Our company runs more than one hundred projects on a single instance server. Besides core IT projects, we have implemented business processes on dedicated JIRA instances to manage high volume (greater than five thousand issues per month) non-conformities for some business lines.

We use this solution for product development and issue tracking.

We use this solution for our scrum team and user story management.

We use this solution for Agile project management and BAU work delivery in sprints / DevOps.

We use this solution for Agile Scrum-Based DevOps on AWS with a Linux, Cloud-Based SaaS environment for mission-critical applications.

Our primary use case is ALM, which is very well supported by Atlassian.

Our primary use case is executing the SDLC.

Our primary use case for this solution is work management and task management. We use this product quite extensively, and we're planning to roll out a module for the Accounts Department to be able to map manpower costs to project work, directly. That is something that we're working on right now.

Our primary use case for this solution is development ticket status tracking. We use it for managing different kinds of projects. This is an online tool, where teams from anywhere in the world can use it.

This software is implemented in the different departments of the company since it allows us to plan, organize and verify or monitor the different projects we develop day by day, thus improving communication and workflow.

Full SDLC, from software development to quality assurance tracking and project management. The applications of JIRA workflow management are endless.