Companies that use Jira (active customer list)

We dug into our own data to find out how some companies are using Jira in sophisticated, interesting ways. We also corroborated our data by asking employees who worked in each of these companies.

Amazon (Amazon Leo)

Satellite Broadband · Bellevue & Redmond, WA · Jira, Confluence, Jira Service Management

Amazon Leo is Amazon's low Earth orbit satellite internet network, their direct competitor to SpaceX's Starlink. The program used to be called Project Kuiper before Amazon rebranded it.

Jira sits at the center of how Amazon Leo coordinates the design, testing, and manufacturing of actual spacecraft. Their Integrated Vehicle Test team in Redmond uses Jira and Confluence to track satellite assembly end to end, so when someone is physically wiring up a test rack or running a test campaign on a vehicle before launch, there's a Jira ticket tracking it.

The unusual thing about Leo's Jira setup is that they run it across three environments at the same time: on-premise servers in their own data centers, AWS cloud-hosted deployments, and SaaS. Each one exists for a reason. Leo's work involves US government programs and export-controlled technology, so a chunk of their Jira data has to live inside regulated environments, with some of it running in AWS GovCloud. SaaS Jira alone wouldn't meet those requirements.

Jira also doesn't run alone. The Productivity Services team that owns the platform pairs Jira with Jama (a requirements management tool used for satellite engineering) and TestRail (for test case management), so they can trace a single satellite component from initial requirements through Jira tickets through to actual test execution.

---

SAP

Enterprise Software · Walldorf, Germany · ERP, Cloud, Business AI

SAP makes business software, the kind big companies use to run their finances, supply chains, and HR. They're one of the largest software companies in the world, with more than 140,000 employees.

SAP uses Jira to coordinate the rollout of its own software at customer sites. When a company buys SAP and needs help getting it running, SAP sends in project managers who track every milestone, budget line, risk, and status update inside Jira, alongside SAP's own planning tools.

The work itself is detailed. A single rollout has financial forecasting, backlog management, and dozens of cross-functional handoffs between consultants, architects, and the customer's own teams. Jira is where all of that lives, so executives on both sides can see whether the project is on time and on budget without having to chase anyone down.

Jira also runs the go-live process inside the SAP Store, the online shop where customers buy SAP and partner software. Every defect, every release task, and every handoff needed to push a new feature into production is tracked there. A missed step at go-live means a broken checkout, so the bar for coordination is high.

When SAP migrates a customer's huge business system from one version to the next, the engineers running the migration log every technical change and every automation tweak in Jira. That paper trail matters, because these migrations can take months and any one change can break something downstream.

---

Adobe

Software Development · San Jose, CA · Jira, Jira Data Center, Jira Cloud

Adobe makes Photoshop, Illustrator, Premiere Pro, Acrobat, and Firefly, with over 41,000 employees building the company's creative, document, and AI products.

Their Jira Data Center installation is, in their own words, one of the largest and most complex in the world. Every Photoshop feature, every Acrobat fix, every new Firefly capability moves through it.

The most concrete use is engineering release coordination. Adobe wires Jira directly into GitHub so pull requests, code reviews, and ticket status stay in sync, and when an engineer ships a fix to Premiere Pro or a new feature to Express, the ticket follows the commit through QA into production.

Security work runs on the same plumbing. Adobe's Product Security Operations team triages findings from bug bounties, SAST and DAST scans, and code scanning, opening a Jira ticket with a CVSS score and an SLA for each vulnerability and tracking remediation through to fix. The same workflow generates the evidence trail for FedRAMP and SOC 2 audits, which matters because Adobe sells to the US government.

Adobe's generative AI products run on the same backbone. Firefly Foundry, the enterprise GenAI offering, uses Jira for customer engagement plans and LLM launches, while GenStudio's PMs in San Jose and Bucharest coordinate the marketing AI roadmap off the same backlog.

---

Cloudflare

Computer and Network Security · San Francisco, CA · Jira, Confluence, Jira Service Management

Cloudflare runs one of the world's largest networks, with servers in more than 335 cities across 120+ countries. The company protects and accelerates roughly 20% of all web traffic, handles DNS for tens of millions of websites, and blocks billions of cyberattacks every day.

The most concrete use of Jira at Cloudflare is the data center build-out. When Cloudflare's deployment team spins up a new data center in one of those 335+ cities, every step has a Jira ticket: the cross-connect installs, the rack-and-stack work with remote contractors on the ground, the BGP configuration, the network cabling. A single new city coming online generates dozens of tickets across hardware, networking, and infrastructure teams that all have to close before the site can take customer traffic.

Cloudflare also runs its internal IT helpdesk on Jira Service Management across the Austin, San Francisco, NY, Singapore, Lisbon, and London offices. When an employee needs an account fix or AV setup for a meeting, the regional IT team works the ticket through to resolution against defined SLAs.

There's also a compliance angle, because Cloudflare sells to the US government and has to pass certifications like FedRAMP High and DoD IL4. The Vulnerability Management team tracks every finding from their scanning tools as a Jira ticket, prioritizes by CVSS score, and drives remediation against required SLAs through Jira. When auditors ask how a vulnerability got found, triaged, and fixed, Jira is the audit trail.

---

Klaviyo

Marketing Services · Boston, MA · Jira, Confluence

Klaviyo is the marketing automation platform that powers email and SMS campaigns for more than 176,000 brands, including Mattel, Glossier, and Liquid Death. The company went public in 2023 and has grown to around 2,800 employees.

Engineering at Klaviyo runs on Jira, and there's a dedicated function inside the engineering org focused on defining and improving how Jira is used: how teams track their work, how dependencies between teams get mapped, and how leadership sees what's happening across R&D. Quarterly planning, team health checks, and the metrics that feed up to leadership all come out of real Jira data, not gut feel from meetings.

The product organization uses Jira to track every feature on the roadmap. Klaviyo is investing heavily in AI-first product development, and Jira sits alongside Productboard and Coda as the single source of truth for what every product squad is shipping. Roadmaps, KPIs, and OKRs all get tracked there, and the cross-functional rhythm with Engineering, Design, Analytics, and the Go-to-Market teams runs off the same Jira backbone.

Procurement and finance lean on Jira too. When Klaviyo rolls out a new procurement tool like Zip or Coupa, or migrates work in NetSuite, they manage the entire change as a Jira-based agile project with backlog management, sprint planning, and release coordination running through the tool.

---

MongoDB

Software Development · New York City, NY · Jira, Confluence

MongoDB is the company behind one of the most popular databases in the world, used by around 60,000 customers including most of the Fortune 100. About 7,700 employees, headquartered in New York.

The most distinctive thing about MongoDB's Jira usage is how much of it lives inside their security and compliance organization. Their Assurance, Risk, and Compliance team owns every security certification MongoDB holds, and they run that work in Jira. Every policy review, every audit task, every risk assessment is a ticket, so when SOC 2, ISO 27001, or FedRAMP auditors show up, the evidence they need is sitting in Jira boards and Confluence pages.

This matters because MongoDB sells to banks, hospitals, and governments who can't use a database without the right certifications. Their Atlas for Government product runs the most sensitive US federal workloads, and the team keeps it compliant with FedRAMP High and DoD IL5+ entirely through Jira. They even monitor what they call "frozen tickets" to make sure nothing critical gets stuck and slows down a federal authorization.

Engineering runs on Jira in a similar way. MongoDB's Site Reliability Engineering team uses it to track every production change, every launch readiness review, and every incident on Atlas, then ties those tickets back to reliability metrics like SLOs and SLIs to figure out what to prioritize next. When a customer's database goes down at 2am, the post-mortem and follow-up work all live in Jira.

---

Capital One

Financial Services · McLean, VA · Jira, Jira Align

Capital One is one of the largest banks in the United States, with over 83,000 employees. They've long positioned themselves as a technology company that happens to do banking, and they run one of the most cloud-heavy technology operations in financial services.

Capital One's Card business runs portfolio management on Jira and Jira Align. Across more than 40 separate portfolios, the team translates every strategic roadmap into Jira projects with defined hierarchies, labor data, and labels. When leadership wants to know who is working on what across Card, the answer comes out of Jira.

The day-to-day work is mostly about keeping the data clean. There's a dedicated function inside Card Tech Analytics that audits Jira projects regularly to fix errors, remove duplicates, and reconcile labor data so the dashboards and reports executives look at actually match reality. They also write Jira Query Language (JQL) and SQL to pull custom views for Card's portfolio managers.

When Capital One reorganizes internally, which happens periodically at a bank this size, the team has to restructure Jira project hierarchies to match the new org chart. That cleanup is part of how the reorg gets finalized, because if leadership can't see their org's work accurately in Jira, they can't plan against it.

---

Allianz

Insurance · Munich, Germany · Jira

Allianz is one of the world's largest insurance and asset management companies, with more than 100 million customers across nearly 70 countries.

What's interesting is how Allianz thinks about Jira. Most companies install it and move on, but Allianz has turned theirs into a branded internal platform called the Jira Master Platform, or JMP, serving roughly 48,000 internal users for project tracking, workflow automation, and issue management.

At that scale, Allianz operates JMP like an internal product. There's a dedicated JMP support team that employees go to when they need help configuring a project, raising a request, or fixing something that's not working. They run a demand management process for evaluating new requests from teams who want something added, and they've built a "Jira champions" network of embedded experts across the company who help their own colleagues use the platform well.

What JMP actually tracks is broader than most Jira setups. Beyond the usual engineering and transformation work, Allianz uses it to track the financial lifecycle of projects. Budget approvals, purchase orders, invoice reconciliation against SAP, and monthly variance analysis all flow through JMP. When a project is approved, JMP tracks the demand. When invoices come in from vendors, they get matched against the original budget in JMP. When finance needs to decide whether a cost should be capitalized or expensed, that decision is tied back to the JMP record. Most companies keep project work in Jira and project finances in spreadsheets or SAP. Allianz has connected the two.

---

Vanguard

Financial Services · Malvern, PA · Jira, Confluence

Vanguard is one of the world's largest investment management companies, serving more than 50 million investors globally with over 18,800 employees across 19 locations.

Vanguard treats Jira as the system of record for team and portfolio management across the Client Experience & Digital organization. New work enters the portfolio through structured Jira intake, work hierarchy is defined inside Jira, and standards changes get evaluated and rolled out from there.

The clearest example is the Quarterly Portfolio Reviews and Quarterly Roadmap Reviews, the leadership forums where executives assess portfolio health, surface risks, and connect strategy to execution. The entire mechanic runs out of Jira: preparation guidance, templates, data expectations, review flows, and follow-up actions all tie back to the same environment. Most companies pull data out of Jira into a separate BI tool for executive reporting. Vanguard treats Jira itself as the artifact leadership looks at.

The AI and data governance program is the other big use case. Inside Vanguard's Chief Data & Analytics Office, the Data and AI Defense team uses Jira to track compliance work against frameworks like NIST AI RMF and BCBS 239, with AI policy assessments, model monitoring rollouts, and the KPIs that measure governance effectiveness all living as Jira tickets.

---

BTG Pactual

Financial Services - São Paulo, Brazil

BTG Pactual is Latin America's largest investment bank, operating in investment banking, trading, wealth management, and digital banking across Brazil, the Americas, Europe, and the UK.

BTG doesn't just use Jira out of the box. They have dedicated Jira developers who build custom plugins and add-ons using Java, the Atlassian SDK, and Spring Boot, treating Jira as a platform they can extend with their own code rather than a tool they configure and leave alone.

Where this really pays off is inside the bank's Automation team, a group of product managers, frontend developers, and backend developers sitting inside BTG's Data & AI area whose entire job is finding repetitive manual work across the bank and building software that replaces it. They use Jira as the backlog for all of it. Opportunities get identified in "discovery" sessions with business teams, where the team interviews stakeholders to find out what's painful, then prioritized against competing demand. Once approved, the work gets broken down into epics and user stories inside Jira, built by the developers, and tracked through to production. So when the bank gets faster at something behind the scenes, this team and this Jira backlog are usually the reason.

A completely different BTG team uses Jira for their Salesforce CRM work. The bank runs Sales Cloud and Service Cloud on top of Salesforce, integrated with their core banking systems, KYC checks, and customer channels. The backlog for building and evolving all of that, from new features to integrations to bug fixes to release deployments, lives in Jira, organized by a dedicated Technical Leader who runs the squad. They pair Jira with Confluence for documentation and Miro for process mapping, which lets them trace any Salesforce change from the business request all the way through to the live deployment.

---

Temenos

Software Development · Geneva, Switzerland · Jira, Jira Service Management

Temenos is a global banking software company serving more than 3,000 financial institutions across 150 countries, from the largest global banks to community lenders.

The most interesting thing about Temenos and Jira is that Jira Service Management isn't just an internal IT tool. Temenos uses it as the customer-facing support portal that the 3,000 banks running their software submit issues, track incidents, and get help through. When a bank using Temenos Transact, the core banking platform, hits a problem in production, the ticket they file lands in Jira.

Because banks expect support around the clock, Temenos runs Jira on a follow-the-sun model. Administrators in Romania, the Philippines, and India hand off coverage across time zones so the customer-facing service desk never goes dark. The same team also runs Jira Assets to track IT configuration data and writes complex automation rules to route tickets to the right product specialists.

Temenos has built custom Jira apps on top of all this using Atlassian Forge, the development platform Atlassian provides for extending Jira. Their developers use both UI Kit and Custom UI with ReactJS to build interfaces tailored to how Temenos and its bank customers actually want to work, then wire those into other business systems through REST APIs.

---

Walmart

Retail · Bentonville, Arkansas · Jira, Confluence

Walmart is the biggest retailer in the world, and behind the stores sits an enormous technology organisation building everything from supply chain systems to the websites and apps customers actually shop on.

Walmart runs Jira and Confluence as the backbone for coordinating tens of thousands of engineers, product managers, and business teams. Their instances have more than 50,000 active users, putting them in the top tier of large enterprise deployments anywhere.

What's interesting is that Walmart doesn't treat Jira as a piece of software they just installed and configured. They have a dedicated Collaboration Tools Engineering Team in Bentonville whose entire job is to build on top of it, writing custom code, automating routine processes, and building web tools, dashboards, and reporting that go well beyond what Jira gives you out of the box. The point of all that custom work is to give Walmart executives a view into what the technology organisation is actually doing, so resourcing decisions, product roadmap calls, and where to invest engineering time get powered by data pulled out of Jira and shaped into something leadership can actually use.

There's also a separate strand of Jira work happening over at Walmart Connect, the advertising business that lets brands reach Walmart shoppers. They run their own Jira administration function supporting hundreds of users in sales, operations, and product, with custom workflows, permission schemes, and automations specific to how the ads business operates. Same underlying tool, completely different use case from the core technology org.

---

HelloFresh

Consumer Services · Berlin, Germany · Jira

HelloFresh is the world's largest meal kit company, serving more than 7.5 million customers across 18 countries with weekly boxes delivering 243 million meals in a single quarter.

What makes HelloFresh's Jira setup genuinely unusual is how much of the food operation itself runs on it. Most companies use Jira for engineering tickets. HelloFresh uses it to run food safety, ingredient sourcing, and delivery scheduling across a global supply chain.

Food safety is the clearest example. HelloFresh's Food Safety and Quality Assurance function covers 11 international markets, and they run all the key processes through Jira as the operational system of record. This includes supplier onboarding, non-conformance management, warehouse inbound checks, inventory management, and shelf-life tracking. When a shelf-life issue gets flagged at a distribution center, the workflow lives in Jira. When a new supplier needs to be vetted, the same thing. For a company delivering hundreds of millions of meals a year, this is how they keep food safe at scale.

Sourcing works the same way. HelloFresh runs a dedicated "INTL Sourcing Jira Board" that governs what they call New Ingredient Development. When a supplier proposes a new ingredient, the feasibility assessment, sampling coordination with the central team, and weekly progress tracking all happen in Jira. Dashboards built on top of the board give the sourcing team visibility into which ingredients are moving through the pipeline and where the bottlenecks are.

Delivery operations use Jira in a more unusual way. When HelloFresh adjusts cutoff times, delivery windows, or pricing across different countries, they document the validation work in Jira as an audit trail. Before a "Go/No-Go" decision is made for peak holiday periods, the Jira record shows exactly what was tested and what the outcomes were. That's not a typical use of Jira. It's Jira as the evidence base for operational decisions that directly affect millions of deliveries.

---

Best Buy

Retail · Richfield, MN, USA · Jira

Best Buy is one of the largest consumer electronics retailers in the world, with more than 74,000 employees and over 1,000 stores across the US and Canada.

What most shoppers don't know is that Best Buy has been quietly building an advertising business called Best Buy Ads. It's a retail media network, the industry term for what Amazon and Walmart have been doing for years, letting brands pay to advertise on the retailer's website, in their app, and in their stores. If you've ever searched for a Samsung TV on bestbuy.com and noticed a Sony TV appearing near the top, that's Best Buy Ads at work. Samsung, Sony, LG, Apple, and the other big electronics brands all pay Best Buy to run campaigns targeting Best Buy's shoppers.

Jira is the operating system for the teams running Best Buy Ads. When a brand signs a deal to advertise, Best Buy's sales and operations teams manage the whole lifecycle from contract to invoice in a Jira-based internal platform that's wired into Salesforce Sales Cloud and Salesforce Media Cloud, covering order entry, campaign setup, delivery coordination, and billing reconciliation.

Best Buy also offers a separate self-service app called My Ads, where advertisers log in and build their own campaigns without needing a salesperson. The internal product and engineering teams who build and improve My Ads run their entire roadmap in Jira, including feature requirements, API integrations with external partners, and the dashboards that show how advertisers are engaging with the tool. The measurement side works the same way: when Best Buy needs to prove to a brand that their campaign actually drove sales, the data science and attribution teams doing that analysis coordinate through Jira.

---

Target

Retail · Minneapolis, MN, USA · Jira

Target is one of America's largest retailers, with over 164,000 employees and more than 1,800 stores.

Like Best Buy, Target has quietly built an advertising business on top of its retail operation, called Roundel. It's a retail media network, which means Roundel lets brands like Pepsi, Tide, and Samsung pay to advertise to Target shoppers. If you search for laundry detergent on target.com and Tide shows up at the top, that's Roundel at work.

Target runs Roundel on Jira behind the scenes. The product managers, engineers, and operations teams who build Roundel's tools track their entire roadmap in Jira, from planning new features to fixing issues advertisers flag to piloting AI features like auto-prioritization of campaigns.

The other place Jira shows up at Target is somewhere you'd never expect: the checkout register. Target has a team called Guest Facing Device Engineering that's responsible for every point-of-sale device in every Target store, more than 400,000 devices across 2,000 locations, all running on Ubuntu Linux. When Target needs to push a software update, deploy a new feature, or patch a security issue across that entire fleet, the team coordinates through Jira alongside Confluence, Git, and Artifactory. So the next time you're checking out at Target and the cashier scans your cereal, the software running that register was shipped through a process tracked in Jira.

---

Nike

Retail · Beaverton, OR, USA · Jira

Nike is the world's largest athletic footwear and apparel company, with close to 100,000 employees globally. Behind the swoosh is a massive logistics and retail operation that designs, manufactures, ships, and sells products in dozens of countries.

Nike uses Jira to coordinate the software that physically moves their products around the world. Their supply chain runs on Blue Yonder TMS, a transportation management system that plans and executes how product gets from factories to warehouses to stores, handling load planning, picking which carrier hauls which shipment, optimizing shipping routes, and tracking shipments in real time.

The product managers and engineers building Nike's Blue Yonder setup run the whole operation through Jira, tracking requirements, configuration, integration work, testing, and deployment there. So when a pair of Jordans gets from a factory in Vietnam to a warehouse in Memphis to a store in Chicago, Nike built the software orchestrating that journey in Jira.

Nike's Store Operations team uses Jira to coordinate what happens inside their global Nike Direct stores. They use it alongside Airtable and Confluence to manage what's launching this week, what needs to be set up on the shop floor, and what training needs to happen.

---

Deutsche Funkturm

Telecommunications · Münster, Germany · Jira

Deutsche Funkturm operates more than 34,600 radio sites across Germany, the infrastructure that makes mobile phone calls, 5G data, television broadcasts, and emergency services radio work for pretty much everyone in the country.

The most interesting part about Deutsche Funkturm's setup is that Jira sits in the middle of the physical tower operation itself. Field planners handling sites across northern Germany use Jira to coordinate site handoffs, track defects, maintain access documentation, and hit construction milestones. When a new cell tower needs to go live or an existing site needs changes, the workflow lives in Jira.

Deutsche Funkturm also runs a 1st Line incident team whose job is coordinating problems across all 34,600 tower sites. When an incident comes in, it lands in Jira and gets tracked against an SLA, with escalations, reporting, and resolution all flowing through the same system.

The same team uses Jira to coordinate with property owners, because Deutsche Funkturm rents the land its towers sit on from tens of thousands of different landlords. Lease renewals, landlord complaints, and construction modifications from the property side all need to be tracked somewhere. That somewhere is Jira.

So at Deutsche Funkturm, Jira isn't tracking software bugs. It's tracking the physical infrastructure that keeps Germany connected.

---

TELUS

Telecommunications · Vancouver, BC, Canada · Jira

TELUS is one of Canada's largest telecommunications companies, with about 37,000 employees. They also run a big healthcare technology business called TELUS Health, which makes the software many Canadian doctors use to see patients.

The first interesting place Jira shows up at TELUS is inside TELUS Health, which builds and operates Electronic Medical Record platforms doctors use to manage patient records, prescriptions, and clinical notes. Two of their main products are called CHR and EMR.

What's unusual is how TELUS uses Jira to manage the actual clinical content inside these platforms. A dedicated team builds and maintains the forms, templates, and clinical workflows doctors interact with every day, and they run that work in Jira alongside Confluence and Salesforce to triage content requests, prioritize updates, and coordinate with healthcare clients. So when a doctor logs into TELUS Health to record a patient visit, the form they're filling out was built and tracked in Jira.

The second interesting place Jira shows up is on the other side of TELUS, in the physical fiber internet build. TELUS has a team called Order Based Drops that manages getting fiber actually connected to customer homes after the neighborhood build is done. They run the entire program through Jira, tracking milestones, partner coordination, customer service escalations, and first-attempt success metrics alongside tools like DOMO and Appian.

---

T-Mobile

Telecommunications · Bellevue, WA · Jira, Confluence

T-Mobile is one of America's three major wireless carriers, with about 39,000 employees providing mobile phone service, 5G, and home internet to millions of Americans.

The interesting thing about T-Mobile and Jira is that the company's Agentic AI program runs out of it. T-Mobile is building an AI system called Agentic Next Best Action (ANBA), which decides what should happen on every customer interaction, and they define every feature for ANBA in Jira as a user story with acceptance criteria covering integration, performance, and security.

T-Mobile also tracks the work to embed AI into the voice call routing network itself in Jira. When an engineer needs to make a change to how calls get routed, the request lands in Jira and flows from there into ServiceNow for implementation, with automation layered on top of this Jira-to-ServiceNow workflow to cut manual steps out of network changes.

The third place Jira shows up is the digital storefront. T-Mobile's eCommerce team manages the entire customer purchase flow, the website, the cart, the checkout, through Jira, tracking every feature, every A/B test, and every funnel optimization there with daily standups and sprint planning running off the same Jira backlog.

---

BT Group

Telecommunications · London, UK · Jira

BT Group is the UK's largest telecom company, with about 73,000 employees. They own several brands that most people in Britain know, including BT itself, EE (the biggest mobile network), Openreach (the company that runs the fiber and copper broadband lines), and Plusnet.

The most interesting place Jira shows up at BT is inside a project called Agentic DMS, BT's attempt to use AI agents to do work that delivery managers and program managers normally do by hand.

The agents read Jira tickets and reason over them to produce useful output. One agent writes status reports automatically by synthesizing what's happening across hundreds of tickets. Another watches for scope creep and flags when a project is quietly growing beyond what was agreed. A third looks for early warning signs that a delivery is going to slip before humans would normally notice.

BT builds these agents on Microsoft Copilot Studio and Azure OpenAI. The agents connect securely into Jira, Confluence, and SharePoint, pull the data they need, and produce their output. Every action the agents take gets logged, and humans stay in the loop on all the important decisions. There's a whole governance layer around the agents too, with red-team testing, least-privilege permissions, and full audit trails so the PMO can trust the output.

At BT, Jira isn't just a place where humans file tickets and update statuses. It's becoming the data source that AI agents read, reason over, and act on.

---

Schaeffler

Industrial Manufacturing · Herzogenaurach, Germany · Jira, Confluence

Schaeffler is a German industrial giant that has been making bearings since 1883, with around 110,000 employees and factories in 55 countries. Their components sit inside the engine, transmission, or chassis of pretty much every major car brand on the road, and lately they've been pivoting hard into electric mobility, robotics, and renewable energy.

The biggest thing Schaeffler is using Jira for is a huge project to overhaul how the company runs HR. They're swapping out their old HR software for SAP SuccessFactors across the entire company, every employee, every country, and they plan and track the whole project in Jira with thousands of tickets covering everything from payroll to recruiting to compensation.

The trickiest part of a project like this is the cutover, the moment Schaeffler flips the switch and turns off the old HR systems and turns on the new ones. A team in Pune, India manages that switch entirely out of Jira, with every step, every dependency, and every risk getting a ticket so nothing slips through the cracks.

Schaeffler also runs Jira itself out of an admin team based in Wroclaw, Poland, who handle account setup, plugins, and support tickets for the whole company. So when an engineer in Germany or a tester in Malaysia needs help with their Jira board, the request goes to Wroclaw.

---

Reckitt

Consumer Goods · Slough, United Kingdom · Jira

Reckitt is the British consumer goods giant behind Lysol, Dettol, Durex, Finish, Vanish, Nurofen, Strepsils, Mucinex, Cillit Bang, and Enfamil baby formula, with around 43,000 employees selling products in nearly every country.

The most unusual part of Reckitt's Jira setup is what they're tracking with it. Reckitt has committed to Net Zero by 2040, and the team running that transition tracks the entire program in Jira. Every workstream toward cutting carbon, every dependency, every milestone lives as a Jira ticket, and the same goes for the ESG reporting work Reckitt publishes in their annual sustainability disclosures.

Most companies treat Jira as a software development tool, but Reckitt has stretched it into one of the central nervous systems of the company. Their factory IT teams use Jira to track projects on the production lines making Dettol and Vanish, and the same setup extends into the R&D labs, where scientists use Jira to manage the platforms chemists work in to develop new versions of Lysol, Strepsils, and Enfamil baby formula. Reckitt's data and digital marketing teams use it too, coordinating work across Meta, TikTok, Google, and Amazon campaigns.

That same approach reaches all the way to Reckitt's consumer websites. The Enfamil.com team runs the baby-formula sites on the Atlassian Suite, working from a prioritized Jira backlog and planning sprints around what new mothers need to find when they arrive on the site.

---

Stanley Black & Decker

Manufacturing · New Britain, CT, USA · Jira

Stanley Black & Decker is the world's largest tool company, behind brands that probably sit somewhere in your garage: DEWALT, BLACK+DECKER, CRAFTSMAN, STANLEY, MAC TOOLS, IRWIN, LENOX, CUB CADET, and HUSTLER. Around 48,000 employees in 60 countries.

The interesting thing about Stanley Black & Decker's Jira setup is how close it sits to the actual products. Their engineers design power tools and outdoor equipment in 3D CAD software like CATIA and manage the lifecycle of every part and product specification through a platform called ENOVIA. Jira sits next to all of that, used to track work on the engineering systems themselves and to coordinate the business analysts, developers, and architects who keep those design platforms running.

The same setup extends into the tools themselves. Modern DEWALT and CRAFTSMAN tools have firmware inside them, the embedded software that controls motors, batteries, and connected features. Engineers in Bangalore test that firmware against bugs and quirks, logging every issue as a Jira ticket. When a connected drill or smart battery misbehaves, the path to fixing it usually starts with a Jira ticket. Behind the scenes, a DevOps team runs cloud pipelines on AWS that talk to those connected tools out in the field.

For a 180-year-old toolmaker, this is a surprisingly modern stack. Jira is the thread connecting the people designing the tools, the people writing the firmware, the people shipping software updates, and the people running the websites where you buy them.

---

John Deere

Machinery Manufacturing · Moline, IL, USA · Jira

John Deere is the world's largest maker of agricultural machinery, the green-and-yellow tractors that work fields across every continent, with around 75,000 employees across more than 30 countries.

The most surprising thing about John Deere's Jira footprint is where it's running. Their largest tractor factory in Germany has a Smart Connected Factory team building modern web apps for the people on the production line, and they track every feature, every bug fix, and every release of these factory apps through Jira tickets, with the team planning sprints, version controlling through GitHub, and coordinating Kubernetes deployments from the Jira backlog.

That same setup extends across the whole company. John Deere has engineering teams running on Jira to coordinate what gets built next. Their Enterprise Data Lake, which pulls customer data, dealer data, and machine data into one shared platform, is run by product managers working out of Jira backlogs, and their Deere.com e-commerce team manages the website's roadmap in Jira too.

For a company that traces its roots to a steel plow in the 19th century, this looks a lot like a software company. Jira is one of the threads holding the modern version of John Deere together.

---

Johnson & Johnson

Healthcare & Medical Devices · New Brunswick, NJ · Jira, Confluence, Jira Service Management

Johnson & Johnson is one of the largest healthcare companies in the world, and J&J MedTech is the part of it that makes medical devices. Inside that sits the Robotics and Digital Solutions group, which builds J&J's surgical robotics platforms, MONARCH for procedures inside the lungs and kidneys, and OTTAVA, a general surgery robot still in development.

The team uses Jira to track all the software work that goes into these robots, but with a twist most companies don't have to deal with. Because the robots are medical devices, the work has to follow two regulatory standards, ISO 13485 and the FDA's 21 CFR 820, which set rules for how medical device software is designed, tested, and documented. Every Jira workflow and status change has to hold up if a regulator asks to see it.

Beyond robotics, Jira runs through the rest of J&J too. The company is in the middle of a multi-year program called Transcend that's consolidating more than 40 separate ERP systems into a single SAP setup, and the team uses Jira to track design gaps, test cycles, and cutover work across that program. Other parts of the company use Jira for finance transformation, AI product development, and lab systems for cell and gene therapy.

---

UnitedHealth Group

Healthcare · Minnetonka, MN · Insurance, Pharmacy Benefits, Health Services

UnitedHealth Group is one of the largest healthcare companies in the world. They run UnitedHealthcare, the insurance plans most Americans recognize, and Optum, which provides pharmacy benefits, technology, and care services to hospitals, employers, and government agencies.

UnitedHealth Group uses Jira to run the technology behind a Medicare and Medicaid program called risk adjustment. In plain language, risk adjustment is how the government pays insurance companies more for sicker patients. Getting it right requires pulling millions of medical records from doctors and hospitals, reading them, and reporting the diagnoses correctly to the government.

The teams building these tools track every feature, every bug, and every release inside Jira. Product managers write user stories there. Engineers pick them up. Quality teams test against the acceptance criteria written in the same ticket. When something breaks in production, the support team logs it back into Jira so it gets fixed in the next sprint.

Jira also runs the work for state Medicaid programs. UnitedHealth helps states like Illinois manage their Medicaid data warehouses, which feed the federal reports states are required to submit on fraud, quality of care, and program enrollment. Project managers leading those state engagements use Jira alongside MS Project and Smartsheet to track scope, dependencies, and risks across vendors.

---

Innovaccer

Healthcare Data Platform · San Francisco, CA · Jira, Confluence

Innovaccer is a healthcare data platform company that sells software, called Healthcare Intelligence Cloud, to hospitals, insurers, and government health agencies. Their software pulls together data from systems the customer already has, like electronic health records, lab systems, and pharmacy benefit managers, so the customer can see one unified view of each patient. Customers include CommonSpirit Health, Atlantic Health, and Banner Health.

When a hospital signs a contract with Innovaccer, the work that follows is a months-long implementation. The team has to connect to the hospital's electronic health record, pull in years of patient data, transform it into a usable format, build reports the hospital's clinicians and finance team need, and go live. These contracts are often worth millions of dollars and involve dozens of people across both companies.

Innovaccer runs those implementations in Jira. Their project managers track every piece of work there: sprint plans, risks, decisions, and the handoffs between Innovaccer's product team, engineers, infrastructure team, and the customer's IT staff. When the customer goes live, Jira also tracks the production tickets that come in afterward, like data feeds breaking or reports needing fixes.

For Innovaccer, Jira is essentially the operating system of customer delivery. Every multi-million-dollar implementation, from kickoff to go-live to ongoing support, runs through it.

---

AdventHealth

Hospital System · Altamonte Springs, FL · Jira

AdventHealth is one of the largest non-profit hospital systems in the US, with around 100,000 employees across more than 2,000 care sites in nine states.

A hospital system that big has a constant identity problem. Every day, doctors start, residents rotate, nurses change facilities, and contractors finish projects. All of those people need access to the right systems to do their jobs, like the electronic health record, scheduling tools, and email, and they need that access cut off cleanly the moment they leave. AdventHealth has a dedicated Identity Management team whose entire job is keeping that flow correct.

That team runs on Jira. They use it to track the work of building and improving the systems that handle accounts, like SailPoint for identity governance, Active Directory for the underlying user accounts, and tools like BeyondTrust and CyberArk for the highly sensitive admin accounts. The team is on call around the clock, because if identity breaks at a hospital, doctors can't log in to patient charts.

---

McKesson

Healthcare · Irving, TX · Jira, Confluence

McKesson is one of the largest healthcare companies in the US, ranked Fortune 8. They're best known as a pharmaceutical distributor, meaning they buy drugs in bulk from manufacturers and deliver them to pharmacies, hospitals, and clinics across the country.

Inside McKesson is a smaller business called Ontada, focused entirely on cancer. Ontada builds software that community oncology practices use to treat patients, including an electronic health record called iKnowMed where doctors document chemotherapy regimens, and clinical decision support tools that suggest treatment pathways based on the latest research. Ontada also sells de-identified cancer data to drug companies running clinical trials.

Ontada runs its software development on Jira and Confluence. They have multiple scrum teams working in a SAFe Agile setup, with a whole layer of program managers, scrum masters, and release managers all coordinating in Jira. Every sprint, every release, and every change to the cancer software is tracked there.

What makes this different from a typical software shop is the regulatory layer. Cancer software has to meet HIPAA, FDA, and ISO rules, which means every change to the software needs a paper trail. Ontada uses formal Jira processes called Release Scope Statements and Scope Change Requests so that when an auditor asks why a particular change was made to a chemotherapy decision tool, the evidence is right there in the ticket.

If you sell a Jira alternative, an Atlassian consultancy, a plugin, or anything else that depends on the buyer caring about Jira, the question that matters is which industries are actually living on Jira versus which ones barely touch it. Generic "tech company" targeting wastes pipeline. We pulled tech stack data on 9.5 million company domains, identified the ones running Atlassian Jira, and ranked sectors by how many times more likely they are to be a Jira customer than the average company.

We collapsed the redundant software-flavored buckets (Computer Games, Data Security Products, Mobile Gaming, etc.) into the main Software Development category to keep the picture clean. The result is a target list: which verticals to prioritize, including some you might not associate with engineering ticket workflows at all.

Sectors most likely to use Atlassian Jira

Multiplier = how many times more likely a company in this sector is to be an Atlassian Jira customer compared to the average company across 9.5 million domains in our dataset. Sub-categories of software development (Computer Games, Data Security Products, Mobile Gaming, Embedded Software, etc.) were collapsed into Software Development to avoid double-counting the same story.

What this tells us

Software Development tops the list at 9.1x with 7,830 customers. No surprise that engineering shops are Jira's bullseye, but the absolute number is worth sitting with: nearly 8,000 software companies in our dataset are running Atlassian Jira. That's the largest single concentrated population of Jira customers in any industry, and it's where any product, plugin, or service related to Jira will find the most addressable demand.

Semiconductor Manufacturing at 7.1x is the highest non-software lift. Chip design is one of the most specification-driven workflows on earth, with massive cross-functional teams coordinating across years-long tape-out cycles. Jira fits that pattern surprisingly well, and EDA tool vendors have been integrating with it for over a decade.

IT Services and IT Consulting at 5.6x with 5,989 customers is the volume play. Consultancies and IT shops use Jira because their clients use Jira. This is the second-largest concentrated population, and it's the buyer with the highest propensity to pay for plugins, integrations, and migration services for client engagements.

Regulated hardware engineering is the strongest non-software cluster. Medical Equipment Manufacturing (5.5x), Defense and Space Manufacturing (5.3x), Medical Device (5.1x), and Aviation and Aerospace (4.3x) all sit in the same band. The connecting thread is rigorous traceability and audit requirements: FDA 510(k), ISO 26262, DO-178C, ITAR. These industries need every requirement, every test case, and every change linked to a ticket. Jira is the dominant tool for that work.

E-Learning at 5.2x is the genuine surprise. Not an industry you'd typically associate with engineering tooling. The likely explanation is that modern e-learning platforms are themselves software products, and content production gets managed through the same ticket workflow as feature development. Course modules, assessments, video assets, and translations all become Jira tickets.

Financial Services at 4.3x with 2,971 customers is the third-largest concentrated population. Banks, fintechs, and asset managers all run substantial in-house engineering teams, and those teams have largely standardized on Jira. The volume here makes Financial Services the most addressable target outside core tech.

Insurance at 4.3x and Banking at 3.7x show the same pattern. Both sectors have large internal IT and digital transformation programs, and Jira has become the default tool for those programs. The lift is real but the customer profile is different from a software company: more compliance-driven, slower decision cycles, more sensitive to data residency and on-prem requirements.

Hospitals and Healthcare at 3.1x with 1,594 customers is worth noting. Most healthcare organizations don't build software, but the ones that do (provider IT teams, health systems with internal product groups, large research institutions) have adopted Jira broadly. The customer base is concentrated in the larger health systems.

Notable absences from the top tier. Real Estate, Construction, Retail, and Hospitality don't appear here because their lift sits at or below baseline. These industries have meaningful headcount but don't run on engineering ticket workflows. If you have a Jira-related product, these sectors are not where to spend outbound dollars.

Analysis based on tech stack data across 9.5 million company domains analyzed by Bloomberry.com. Multiplier calculated as observed Atlassian Jira adoption rate divided by expected adoption rate based on full dataset baseline. Atlassian's own domain was excluded. Software-flavored sub-categories (Computer Games, Mobile Gaming Apps, Data Security Software Products, Embedded Software Products, Computer and Network Security, Data Infrastructure and Analytics, Information Technology and Services, Technology Information and Internet) were collapsed into the main Software Development category to avoid double-counting. For those very technical, we ran Elasticsearch significant terms aggregation queries on our index.

If you sell a Jira alternative, an Atlassian consultancy, a plugin, a migration service, or anything else that depends on the buyer caring about Jira, the worst thing you can do is pitch the wrong job title. Spray-and-pray to "engineers" wastes pipeline. We pulled 339 million job postings, found the ones where employers explicitly demand Jira proficiency, and ranked every job title by how much more (or less) likely it is to mention Jira than the average posting. The result is a target list: which titles to put at the top of your outbound, and which ones to skip entirely.

Why we are not just ranking by popularity

Ranking job titles by raw Jira mention count gives you Backend Engineer first, then QA Engineer, then Backend Engineer again. Other analyses do exactly this. Those roles have a lot of postings in general, so of course they have a lot of Jira mentions. Not interesting.... AT ALL.

The multiplier below answers what actually matters: a job posting for this role is how many times more likely to mention Jira than the average job posting across all 339 million postings we track.

Job titles most likely to use Jira

Multiplier = how many times more likely a job posting for this role is to mention Jira proficiency compared to the average job posting across 339 million postings in our dataset.

What this tells us

Agile Coach tops at 110x, and that is genuinely striking. A posting for an Agile Coach is more than a hundred times more likely to mention Jira than the average job posting. Agile Coaches don't just use Jira, they live in it. Sprint boards, ceremonies, velocity tracking, retrospectives. The tool basically defines the role.

QA Engineer at 60.5x is the second clearest case. Bug tracking and test case management have been Jira's home turf since the beginning. If you build a product that competes with Jira, QA is the hardest persona to pry away.

Project Manager (IT) at 38.3x and Business Analyst at 28.9x are the next tier. These are the "ticket workflow" roles, the people whose daily output is Jira tickets and whose meetings revolve around the board.

Technical Writer at 32.8x is the surprise of the list. Documentation roles are tightly woven into engineering ticket flow, often docs-as-code workflows where every doc change is its own Jira ticket. Higher than Product Manager, which is unexpected.

Backend Engineer is the largest absolute population at 35,401 postings. The lift is "only" 13x, lower than the specialists, but the volume is the largest of any role on the list. If you're sizing the addressable market for a Jira-related product, this is your biggest single bucket.

Job titles least likely to use Jira (where you might expect them to)

The more interesting finding is which white-collar roles are not in the Jira ecosystem. We filtered to office and knowledge-work roles only and ranked by how far below baseline their Jira mention rate falls.

Multiplier = ratio of this role's Jira mention rate to the overall mention rate. A multiplier of 0.10x means a job posting for this role is one-tenth as likely to mention Jira as the average job posting.

What this tells us

Three big "Jira-free zones" emerge in white-collar work.

Sales is the most underindexed cluster. Account Executive at 0.017x, Director of Sales at 0.05x, Manager of Sales at 0.06x, Banker at 0.027x. Sales lives in Salesforce, not Jira. The only sales-adjacent role that breaks the pattern is Sales Operations Specialist, which makes sense: ops people do the systems work that links sales tools to engineering tools.

Finance and accounting are nearly as absent. Accountant at 0.20x, Controller at 0.24x, AR/AP at 0.35x, Tax Specialist at 0.28x, Underwriter at 0.12x, Financial Advisor at essentially zero. Finance lives in NetSuite, Oracle, Workday, and Excel. The exception that proves the rule is Financial Systems Analyst, an IT-adjacent finance role with high Jira lift.

HR and recruiting follow the same pattern. Recruiter at 0.09x, HR Business Partner at 0.23x. HR lives in Workday and Greenhouse. The exception again is the systems-adjacent role: HRIS Analyst.

The boundary is clear. Jira owns the "build software and manage projects" domain. It has not crossed into the records-of-business systems: CRM for sales, ERP for finance, HCM for HR. The only place Jira penetrates those domains is through systems-analyst roles that bridge into IT work.

Analysis based on job posting data across 339 million postings analyzed by Bloomberry.com. Multiplier calculated as observed Jira mention rate for the role divided by expected mention rate based on full dataset baseline. Foreground set defined as postings containing phrases like "use Jira", "experience with Jira", "proficient in Jira", and similar. Atlassian's own postings were excluded. For those very technical, we ran Elasticsearch significant terms aggregation queries on our index.