We use Jira primarily for project management within the organization. It helps us manage tasks, bug management, and tracking tickets effectively. We assign tickets to individual team members and track them easily.

We manage our sprints and backlog using Jira.

My primary use case involves creating tickets and tracking them in Jira. I am responsible for planning iterations and PIs, and I make use of the AI features for summarizing tickets.

We follow an Agile framework and use Jira for sprint planning and management.

I use Jira for sprint planning and tracking projects. I can create boards on it. And then I just have backlogs, and I just basically plan and sprint for the next two weeks, and you just put anything on the to-do list, doing, and done through the board. So it's very simple. It’s all drag and drop. There’s nothing too complex around it. 

The main thing is making sure whatever you're planning for your sprint is covered there, and then you can run reports after that.  Sometimes, the key issue I've seen with project failures is when the sprint planning isn't comprehensive enough.  It’s not being covered. But generally, it's very similar to Microsoft Project, in some ways because you can still create those Kanban boards and run things, but nothing too crazy.

I use Jira for project management. 

I use Jira in many cases when developing software. For example, I often use it for gathering software requirements, checking management, and issue tracking. Sometimes, I use it for planning my software development. I create some pictures and activities for my software planning, so I usually use Jira for my entire software development life cycle.

We are using Jira for scrum, specifically for Agile Scrum. Most of the tasks are in Jira, including the dashboards and reports.

My company doesn't use Jira for service desk management. My organization uses Jira in areas like user stories, ticket tracking for work, dashboards, and kanban boards.

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 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.

We use the solution for secure software development. Additionally, we use the service-based system.

I use Jira for maintaining our user stories, creating defects, and tracking progress. It's a part of my daily workflow. We have a dashboard where we manage stories within sprints, see backlog items, and keep track of both open and closed defects.

I use Jira to schedule tasks, customize them, and track progress within sprints. We follow a two-week sprint structure and manage all our tasks within Jira accordingly. We use it in the defense industry, and our applications are related to satellite communication. 

We use Jira for ticketing purposes, project management, and writing stories, epics, and milestones.

We use Jira for various purposes. Firstly, we use it to gather requirements by raising tickets and tracking them in the system. Additionally, we utilize it for bug-tracking. 

I have managed various projects using Jira, including tasks for the government, the environmental sector, education, and donation applications. I have also worked on multiple websites for marketing and search engine optimization.

We are using the solution for project management.

We use the solution primarily for the IT development processes since we also develop some internal software and integrations. We use it for IT support. We also use the project management features. We help create some custom projects within Jira and assign or dedicate some of the projects to top-level projects. Some are epic projects. We have our own custom project structure within Jira.

Jira is used for field management and task assignment. We use Jira on the project management side. We also use storyboards for planning and scheduling. It can be used for tracking and managing issues. It provides a dashboard showing what's open and what's closed. We can access all these details there.

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.

I use the solution for agile project management. We use it to break down the project into tasks. 

I use it for hours tracking with Tempo login, task management, project management, and time booking with the Tempo plugin.

ira is a very complete tool in the tech industry, helping in deploying software. Jira is a very strong tool for a corporation with a team to track and monitor all the tasks that have been defined within a project. It helps teams work and collaborate faster to improve performance. 

We use Jira as a communication tool for tasks and epics. Everything is in one place in the ticket, and it's helpful to communicate with the team. We don't have to use Slack and other platforms to track information related to tasks.

We maintain all space-related information in Jira. We track all stories and add tasks to identify specific services. We pull the relevant functions onto the screen. We follow a two-week sprint cycle, completing sprints accordingly. We proceed to make a release. We conduct testing activities, whether manual or automated. If bugs are identified, we fix them. The customer story remains in the loop until we move to the release cycle. Upon release, developers can automatically deploy the code. After deployment, we proceed with user acceptance testing and move to the front end.

I use Jira in my company for my projects or the tasks assigned via the tool. I also use Jira as a scrum tool.

We are using the product for general task management, largely. From a software development community perspective, obviously, we use the task management piece - the foundation to what leads into the development and the CI/CD pipelines and et cetera. Outside of that, it varies widely. At its very core, it's task management, however, then it's used by various functional areas within the company. For example, we have contracting and procurement that utilize it. And we have marketing that uses it and security, IT security, audit, compliance. Various functional areas across the company use Jira. We use it a lot. More and more business teams are using it today than were previously.

We also use it for reporting. With task management comes the Jira out-of-the-box reporting. We had Advanced Roadmaps before it was included in the product. And now that it's just rolled into the Data Center product, you obviously don't have to pay for it specifically anymore, however, that's the most scaled reporting that we have. Then, as far as any other apps are concerned, we really just use time and status for measuring continuous flow and have more of a Kanban approach. Of course, some workflow, add-ons, and things of that nature to add some value such as training for Jira.

I'm less concerned about marketplace apps due to the fact that, whether you go to Azure DevOps or Microsoft, or whether you go to Atlassian, there are countless apps out there that will extend the application itself. 

We use it for requirements gathering. We raise our tickets; it takes tickets in the engine. We also use it for bug tracking and integrate it with the X-ray for testing.

I use Jira in my company as a project management and software development tool. We use Jira in our company to document all of our requirements and releases in relation to project management and manage the agile lifecycle management of our products.

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 have different software projects. I primarily use Jira to define and plan projects for agile-based project management. We use different aspects. We have scrum-based management for some projects and different systems for others.

I have used Jira for defect management and issue management. This includes defect categorization, defect analysis, and defect summary, as well as exporting the defects. I have primarily used it from a user side perspective in both ITSM and agile delivery contexts.

Jira is used primarily for ticketing, escalations, and tracking work in progress. It is also integrated with other tools within the company. Additionally, we open Jira to customers for ticketing purposes.

We use Jira for project management and tracking. 

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

I use Jira for project management. I track all my projects through Jira, including the resources, the time, the deadlines, or the roadmap. For me, it's the tool to check the status of the project. If we have time to get more people on the team, we can use it to show the up-skilling and the availability of the team.

We use Jira for project management.

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.

I am using Jira for some programming-driven planning and PI planning system, but I have just started using it for that. I am primarily using it for some projects.

I'm serving as an enterprise agile coach, so I work with a team to help them use Jira. I'm not really sure what the exact data subjects are, but I mostly look at what the team is doing and if they have updated, then they let me know. I'm not using Jira for my own instances, but for my team's. I'm helping the scrum masters and the product owners.

The solution is deployed on cloud.

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 for client ticketing. We have managed services agreements with clients, and we use it when they have issues. It consolidates well with their IT ticket system. We are the first pass on the ticket issues. If it seems that a ticket belongs to them, we can easily pass it onto their system and their people. So, it is a ticket system for our clients.

We are using its cloud version, and it is hosted in Atlassian's cloud system.

We basically use the solution for trying to develop a product end-to-end. It's assisting us in having hardware and software come together.

We're using JIRA in combination with Xray as a test management tool.

The Xray module gives us test management capabilities, right. Where we can store tests and test executions and so on. That's basically where we moved our test out and we left Quality Center behind. 

With Jira, basically, you have a story. You try to estimate the story and then you have to try to have coverage for each story with test cases. We sometimes use it for our automation perspective. We're using the JIRA Xray API to write bad test results into the tool, through an API call rather than going through the UI. Our continuous testing pipeline in GitLab will automatically update the test results through the Xray API. That's it.

My primary use case for Jira is agile development as a systems integrator. The best use case is to pile up the backlog and then assign those backlogs stories to the user stories, which will be filtered into a sprint. Each story is then assigned to a cross-functional team member for tracking the dependencies and progress on the user story. You can also tag the user story to a particular team.

Similar to the whole solution stack, we use Jira for security and for operational data storage. We also use it for custom-made API structures, moving data from the cloud to legacy on-prem infrastructures so we can use it to develop failing interfaces. We're customers of Jira and we license the solution. Our company has a form of strategic alliance where we buy the product, pay the fees and use the solution. I'm a senior technical project manager.

I use it to manage my scrum projects and some of the Kanban projects.

In terms of version, they have been updating it every three weeks. It is a kind of a sprint that they do, just like Google Chrome. So, there is no going back and forth. We use a cloud-based application. So, it is always the updated one.

The type of cloud depends on the client. I've been through all kinds of situations: completely public, semi-public, and private. If it is a public cloud, then it is directly from Atlassian. They are providing it. So, there is no middleware.

It's pretty much for engineering development, Scaled Agile purposes for engineering development, for managing basically the epics and the stories and the capabilities and everything that we have to deliver in sprints. We're not using it as a ticketing tool or anything like that, for operations. We're using it purely for managing the development stuff in a Scaled Agile manner.

We are using it for project management.

I use the solution in my company as an ITSM tool. Our company's service desk and those working with the engineering team use the tool.

I am an Agile coach and consultant, and my clients use Jira to manage Agile teams, including tracking and gathering reports on performance at the team level as well as the team-of-teams level.

Since I work with different companies in my consulting work, there are different versions and implementations of Jira that I deal with. Most of the time I work with Jira on-premises, although I have worked a few times on the cloud edition.

In the near future, I most likely be using Jira Portfolio instead of the regular Jira because that will be my new responsibility.

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

For the past two years I have been administrating Jira for our enterprise organization, in which there are about 300 end users. Apart from an administrator, I'm also a hands-on Jira user now.

Our main uses for Jira include asset management, project management, Scrum project tracking, Kanban projects tracking, and cost tracking, as well as productivity measurement.

The solution allows us to escalate issues from the end-user customer very easily. For example, if they're trying to access our PayPal page, and they're getting an error, we will do the basic troubleshooting. If the problem persists, then we will file the case and we will send all the stuff to reproduce the issues, including the ID, everything, using the Jira tool. We will create the task and it will go to the Level Three engineering team. They'll create that bug and route it to the Product Development team. Since the time I've raised the ticket, there are lots of options and there are lots of products that we may be using. That includes understanding what is the issue, what is the SLA, what is the issue criteria, et cetera. We can create and submit issues based on multiple types of criteria.

We primarily use the solution as an ALM, an application lifecycle management tool. 

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.

The solution is primarily used in a scrum setting for creating all the features, topics, epics, stories, backlogs, and helps manage the scrum.

We are using Jira mostly for the workflow dashboards for our projects. For example, for now, we are using the Kanban boards at team levels and also between team cooperation levels.

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.

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.

We are primarily a software development company. We work on some very specialized software for the government. So, we use Jira as our primary bug/issue tracker. We are also looking to put some add-ins in it to help with configuration management.

We also use it for configuration management and task assignment, but that's all within the bug tracker itself. What's good for us is that we are not doing all of that in three different applications. That's very useful. I'm sure larger businesses can find other uses and plugins for it, but right at the moment, Jira is fulfilling our needs.

We are using Jira for ticket management.

We primarily use the solution for all issue reporting. The business uses it and we use it in IT as well. Any issue, anything from the help desk to software issues use Jira. It can house test plans, test sets, test executions, and provide some reporting. It's the reporting that's important for us.

We are using primarily using Jira for the project and issue tracking mostly.

Currently, we're using it as a tracking tool. It helps our development department operate more efficiently while enabling the business side of the company to understand and track things better. For example, if we get a requirement from the business side, they don't tell us the status of the current cover every time. So basically what we do, if we complete development or make it to the development phase, then we can change the status in Jira. If the other departments want to see the progress, they can go to the Jira dashboard. So this reduces the amount of necessary communication between the business side and developers. Developers can mainly focus on the development instead of having to answer questions from other departments.

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

Our primary use case of Jira is for tracking corporates and for new test cases where we need to execute monthly releases. We use it for test management purposes, whether for tracking or test use cases in their different cycles. We log everything on Jira and are very dependent on it. We are customers of Jira and I'm senior quality assurance person.

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 primarily use the solution for project management. 

We primarily use the solution for project management. 

We use Agile Practices, so we track all our projects in Jira. When the project starts, we start putting all the user stories there. If any user story has any down the line task or user career task, we attach those Jira stories to our Confluence pages as well. So we maintain Confluence pages as well as Jira together as a story. The requirement and the Jira story are linked together.

I primarily use the solution for use cases and make sure that our tasks and priorities are getting done.

We are using the recent version.

We use it for story and sprint planning, as well as for reporting. 

We use Jira for task tracking, sprint planning, and backlog.

We have been using Jira for schedule management as well as for making updates to our projects. I mention this in my capacity as a project manager. I most recently used the solution this year and did so for scheduled management of our varied tasks and projects. JIRA is actually used to put together an entire portfolio for each one of the teams, meaning for everybody. The solution listed each of our projects individually, with us needing to provide daily and regular updates. 

I work with a credit rating company in the US. As a scrum master and project manager, I have to make sure that all the impediments are removed for the team. I work with product owners to make sure that all initiatives requested by our stakeholders, who are mainly compliance and regulations people, are moving in a timely manner.

I use Jira to make sure that we are capturing all the work that is requested, and it is progressing in a timely manner. I am in charge of a squad called Core Operations Reporting. A squad is usually focused on one or two initiatives. The goal of our squad is to automate regulatory reports as much as possible. I talk to our stakeholders to ensure that any errors in credit ratings are dealt with in a timely manner. A lot of these requests are ad hoc, and we prioritize them in sprints in Jira. 

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.

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.

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 use the tool to review code quality and communicate with the QA team. I also use the product to raise tickets with my senior management for issues I cannot resolve.

My company uses the product for the user storage it provides. The tool is also useful for requirements management and test management processes. The product is also useful to track the hours people in the company have spent on testing and test logging.

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 are using Jira for the internal project and issue management or tracking.

Its use case just depends on the company I've been with at the time. I have used it for defect management, development processes, and status. At one point, we ran our entire risk platform out of it as well.

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 are using Jira for task management.

Jira is used by my clients across their organizations. They use it for everything related to IT solutions.

We use it for project organization, workflow, and team collaboration. 

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.

My primary use case is using the boards in working stories for freeing up the backlog and assigning tasks to my developer team. 

No other stats of graphics or reports from Jira are used. We use Grafana instead of that.

I use the solution for software project management and software lifecycles. Jira covers the entire process from requirement analysis to deployment. 

My primary use case of Jira is as our project management tool for monitoring and planning.

We are using it to organize most of our software development processes. 

Being a cloud solution, we usually have the latest version, but sometimes, we get a pop-up saying that there are some changes in a menu or some new features are there.

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

We are using Jira for requirement and defect management. Not for DevOps purposes, only application development.

As a lead consultant, I assess the testing maturity and suggest how our clients can improve what they're doing. I also carry out training sessions for Jira and other solutions as to how they can effectively use the solution. 

We use JIRA for the management of tasks in IT. We are in the process of implementing our JIRA service desk and using other software for development, such as Bitbucket.

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

I'm head of the IT service desk, and we're using it to track IT tickets from the users. If there is an incident or someone requests information or services, we handle all these requests through Jira Service Desk.

We use Jira in our organization for lifecycle management.

It is helpful for bug tracking in software development. If developers are doing some work and testers notice some defects, they can flag it in JIRA. For example, I track my day-to-day work in JIRA so that others know what I'm working on. They can look at JIRA and don't need to contact me. From JIRA, they can find out that I am working on this project and spent two days on it, etc. It's used for so many things, like task management, bug tracking, and release management. 

JIRA is not for deployment. For deployment, you are going to use some tools like Jenkins. It's meant for all the features that are going into that deployment. 

Different teams within the company use JIRA. For example, everybody in the engineering section uses it, so altogether, that's around 200 people.

We use Jira for project management for the development teams. Additionally, we do backtracking and managing the backlog but it is more of a development team tool.

We use Jira for enterprise planning.

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.

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 primarily use the solution for software management. 

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

We are using it for service management, change management, project management, and tracking the changes.

We are basically using it to support the UAT tasks. We are also using it for IT support task handling and working together as a team in our company. 

At my workplace, we are using its most updated 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 are using it for bug tracking and new feature development. We have its latest version.

We started using it in the eComm team for the website and all the digital projects. At the beginning was Jira for software development and the Confluence to move the communication away from our mailboxes. Now, we're also using it for marketing and campaign management. Confluence is now our single source of truth and, in general, we are using it in much more content-based projects.

We use Jira every day for tasks like tracking product deployments, mapping it to the tools that we use, and sprint tracking. We also used it for audit purposes, where everybody goes back to that for details about each user story.

Each sprint tracking is done in there, as well as the other product-related activities

All aspects of Jira administration help with respect to QA development and deployment.

When you are engaged in an Agile development environment, most of the handling and tracking of the stories are handled in Jira. It can also be used for handling and tracking requests in a ticketing system.

I am a consultant from the quality and design part of the work that we do, and I help people introduce tools into their system. Currently, I am only working with one customer that is using Jira. In the past, I have had five or six who were actively using it.

It is used by the agile teams for product development and feature management.

We use this solution because it comes with some of the products that we are using. It is a part of the package. Our usage is quite basic, and we have not finished exploring and deploying the whole solution.

We are basically using it to register all the requirements and issues so that we can track them and control the flow and different states. We also use it for reporting and configuring dashboards for portfolio management.

It is a SaaS solution, and we are using its latest version.

I use the Jira app, not the desktop version. 

I work at a university and we use Jira to create tickets, epics, and stories. We link Jira to spec documentation with Confluence. We can also link it to TestRail.

Within the university that I work for, there are roughly 4,000 people using this solution — all staff members use it. 

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 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.

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.

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

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.

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.

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 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 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.

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.

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

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 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. 

I have worked with Jira for agile scrum projects. Jira is a good tool that helps you track and monitor all your stories, scrum updates, and Definition of Doneness (DoD). We can track everything we need to track and pull the reports from the Jira tool. Based on the team's activity, we can monitor, track, and update the tasks we have assigned through Jira. We also use Jira for sprint planning.

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 use Jira to manage what is happening in our projects, such as application development lifecycles.

We use Jira for ETCM. It's for ticketing with QRadar.

Our primary use case is for project management and defect tracking. We are customers of Jira and I'm the quality manager. 

We use it for Kanban boards, bug reports, and some workflows.

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. 

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

We are using Jira for user requirements, our development, and for our agile and scrum requirements. We create scrum boards for our projects.

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.

We use Jira as a help desk, an IDSM. We use it on a daily basis. Every ticket gets opened on it.

Our company is a consulting company and then we are an Atlassian partner as well. Therefore we use many functions of Jira. It's sometimes project management and sometimes to communicate to outside customers.

We primarily use the solution for our own projects.

We use this solution to manage our projects.

We use Jira to manage our software development lifecycle. Additionally, it can be used to communicate between teams and as a management tool, it has many abilities.

We use Jira for our in-house projects. We use Jira Cloud and Bitbucket. We are not actively using Confluence.

I'm a consulting company. I provide solutions for many companies, and in some cases, I implement Jira. DevOps is something else that I provide for my clients.

Our clients range in all sizes. I have microscopic clients, such as a one-man company, and on the other end of the spectrum, I have the New Zealand government, for example.

We mainly use the solution for project management. We are using Jira for our software development purposes only. Usually, we create a Jira project for each project and develop it according to its size. We assign team members who will belong to those projects, each project. Then, we manage everything using Jira.

Basically, the main purpose of using Jira is just planning and then checking issues. That's all for now.

Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so.

We regularly check the tasks assigned to us, day by day, and create a work log in that task according to what has been done.

You can check today's task assigned to you by using a custom filter, which you can create on your own. We can also make a customized dashboard user-wise.

Upper-level management can analyze the chart and get an overview of the project, giving them the ability to estimate the budget and release date of the project.

Our testers and QA teams use this tool. 

Our primary use case is for project management, guiding the teams in our company. The solution allows you to create Scrum boards to deliver all the acquired stories within the Scrum Sprints. It also adapts to any other Jive methodology, like Kanban, and helps the creation of roadmaps for the software, production and implementation. We use it for day-to-day tasks, managing our stories, assigning tasks to different developers, and even integrating it with other system control tools to link the story's details. We are customers of 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.

Most of our company is using Jira for IT projects. We had an internal project with which I was involved, and I touched on it a little bit. We have its latest version.

We are using it for project management. We have cloud and on-premises deployments of this solution, and we are currently using its latest version.

We are mainly using it for project management and issue tracking. It is used by development, QA, and IT operations. It really goes through the whole gamut of project management.

We are not using its latest version. We are usually a little bit behind on versions.

We primarily use the solution for collaboration purposes.

We use the solution to track all projects and management activity.

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. 

Our primary use cases for this product are project management, customer relationship management, internal management, and collaboration.

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.

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 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.

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

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.

We are using Jira to manage our development sprints.

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

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

We use Jira primarily for Agile development and change management.

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 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 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. 

• Agile, scrum project/sprint planning
• Bug tracking
• Workflows which help track the current state of tasks.

Requirements management.

Jira is the best project and defect management tool. It works very well for all types of software methodologies or cycles. Communication is very clear to the whole team members. My team relies on this software to keep track of what we are doing. It has lots of nice features that we use such as to link issues to one another, link tickets, put labels of versions to be released, and story points. As a QA person, I also use the filters a lot to find issues that are assigned to me or have been reported by me.

Team level agile project management.

It is easy to assign books, story styles, move across platforms and to different stakeholders while using this platform.

It possesses excellent customization and serves the basic requirements: multi-project, products, customers and multi-level of users.

We use it mainly for Scrum management.

We are working in the safe channel process in the IT part of the bank. It is a good experience overall, but the look and feel for the user is not good.

The primary use is task management. It has performed okay. It is easy to configure and maintain. It's quite simple to track tasks, then link with other applications/solutions from Atlassian, like source codes.

We use JIRA for maintaining tasks and bugs. Overall, we love using JIRA because it performs very well with a lot of tasks and a lot of dashboards.

The primary use case is task management within the team and the company, as well as version management and bug management.

• Running agile deliveries with dispersed teams. 
• The projects were typical agile, changing requirements frequently.
• JIRA facilitated story management perfectly.

We use it for backlog management, sprint planning, requirements management, Scrum, conducting Scrums, and all of our agile stuff.

It's really for Agile projects with storyboards, and then defect management.

The performance has been okay.

We run pilots and product development using this for Agile and Scrum applications, in mechatronic product development.

It has performed well so far. We like it, we would like to expand it.

Managing our entire product development life cycle, as well as all test cases and test runs. That include at least 4 developers, 2 business analysts and 2 testers, all working on sprints. 

JIRA is an issue tracking application, it in global development projects. JIRA helps teams to track and accomplish the items that need to be The great feature about JIRA is you can store the activity happening around an asset in one placeJIRA is useful in project management. It can reduce the rework in enterprise projects. You can also use JIRA Core for Project management, Task management, Process management, HR, Marketing, Legal and Finance projects. JIRA Core can be as per business projects need.

We used JIRA for:

• Writing down requirements and stories.
• Analysis
• Creating tasks, subtasks, and defects.

It also helped tracking the sprint process more efficiently.

JIRA is the project management system in my company. We use it on a daily basis. It is the main instrument widely used by QAs, Product Developers, Technical Writers, and Project Managers

We use Jira strategic management and overall best practices management.

We use it for IT project management. We manage the timelines and resources, mainly people resources.

We use it mainly for logging defects and tracking them.

Our primary use case for JIRA is for project tracking to see where our development team productivity is.

I am generally managing development teams in a position of delivery lead. I have also been involved in several positions where I acted as a Jira administrator, setting up delivery processes and production support.