Bugzilla Scraper - Bugs, Status, Severity & Owners

Scrape any Bugzilla instance in bulk, including Mozilla, Red Hat and Gentoo. Extract bug ID, summary, product, component, status, resolution, priority, severity, platform, reporter, assignee and timestamps to CSV/JSON. No API key, no login.

---

What does the Bugzilla Scraper do?

This Actor turns Bugzilla data into a structured dataset. You point it at one product or several trackers, open bugs only, it walks the result pages one after another, and it writes one clean row per bug into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

Bugzilla ships a REST API that every public installation exposes without a token, so one configuration works against Mozilla, Red Hat, Gentoo, Apache and any self-hosted tracker. The Actor asks for an explicit field list rather than whole bug records, which keeps a five-hundred-bug page in the kilobytes instead of the megabytes. Pagination is followed automatically until it runs out of results, hits your page limit or hits your Max items cap, whichever comes first. Every row is de-duplicated across the whole run, so you are never billed twice for the same bug.

There is no API key, no login and no browser involved. That keeps runs fast and cheap, and it means you can schedule the Actor without worrying about credentials expiring.

Who is it for?

• QA and release managers tracking open defects by component.
• Security researchers surveying disclosed issues across projects.
• Engineering managers measuring resolution rates over time.
• Open-source maintainers exporting their own backlog for analysis.
• Researchers studying how large projects triage defects.

Use cases

• Export every open bug for a product and group them by component.
• Measure how long bugs stay open by comparing creation and resolution dates.
• Find high-severity bugs that are still unassigned.
• Track which components attract the most defects.
• Build a defect dataset for analysis or a quality dashboard.

Why use this Bugzilla Scraper?

• 🔑 Keyless — no account, no API token, no cookies to paste.
• 📦 28 fields per bug — everything the source exposes, already typed.
• 📄 Real pagination — it walks page after page instead of returning the first screen.
• 🎯 Precise caps — Max items stops the run exactly where you want it, so the bill is predictable.
• 📊 Export anywhere — JSON, CSV, Excel or HTML, plus the Apify API and integrations.
• 💸 Pay per result — you pay for rows you actually receive, with no platform fees to calculate.

What data can you extract?

Every run produces one row per bug, with these fields:

Field	Type	Description
instanceDomain	string	Domain of the Bugzilla instance this row came from
bugId	string	Bug number
summary	string	Bug summary line
bugUrl	string	Direct link to the bug
product	string	Product the bug is filed against
component	string	Component within the product
classification	string	Classification the product belongs to
status	string	Current status, e.g. NEW, ASSIGNED or RESOLVED
resolution	string	Resolution when the bug is closed
isOpen	boolean	Whether the bug is still open
priority	string	Priority as set by triage
severity	string	Severity as set by triage
platform	string	Hardware platform the bug applies to
operatingSystem	string	Operating system the bug applies to
version	string	Product version the bug was filed against
keywords	string	Keywords, separated by a pipe
reporter	string	Account that filed the bug
assignee	string	Account the bug is assigned to
createdAt	string	ISO timestamp the bug was filed
lastChangedAt	string	ISO timestamp of the last change
resolvedAt	string	ISO timestamp the bug was resolved
dependsOnCount	number	Number of bugs this one depends on
blocksCount	number	Number of bugs this one blocks
duplicateOf	string	Bug this one was closed as a duplicate of
votes	number	Votes cast on the bug
query	string	Filter this row came from
page	number	Result page the bug appeared on
scrapedAt	string	ISO timestamp of extraction

Output example

{
  "instanceDomain": "bugzilla.mozilla.org",
  "bugId": "69938",
  "summary": "Downloads are stored in $TMPDIR|$TMP|$TEMP|/tmp first and then moved to the selected path only after the download\u2026",
  "bugUrl": "https://bugzilla.mozilla.org/show_bug.cgi?id=69938",
  "product": "Firefox",
  "component": "File Handling",
  "classification": "Client Software",
  "status": "RESOLVED",
  "resolution": "WONTFIX",
  "isOpen": false,
  "priority": "--",
  "severity": "normal",
  "platform": "x86",
  "operatingSystem": "All",
  "version": "unspecified",
  "keywords": "dataloss | helpwanted",
  "reporter": "nitro_jawt@yahoo.com",
  "assignee": "nobody@mozilla.org",
  "createdAt": "2001-02-23T08:26:07Z",
  "lastChangedAt": "2020-05-07T12:11:06Z",
  "resolvedAt": "2017-05-10T09:10:50Z",
  "dependsOnCount": 3,
  "blocksCount": 8,
  "duplicateOf": null,
  "votes": 177,
  "query": "product Firefox",
  "page": 1,
  "scrapedAt": "2026-09-21T10:18:44.902Z"
}

How to use

Option A — one product

{
  "bugStatus": "any",
  "instanceUrls": [
    "https://bugzilla.mozilla.org"
  ],
  "maxItems": 2000,
  "maxPagesPerInstance": 4,
  "product": "Firefox",
  "searchText": ""
}

1. Open the Actor and fill in the first field.
2. Set the page limit and Max items to bound the run.
3. Click Start, then export from the Output tab.

Option B — several trackers, open bugs only

{
  "bugStatus": "NEW",
  "instanceUrls": [
    "https://bugzilla.mozilla.org",
    "https://bugzilla.redhat.com"
  ],
  "maxItems": 1000,
  "maxPagesPerInstance": 2,
  "product": "",
  "searchText": "crash"
}

Everything in the first field is processed independently, so you can batch several targets into one run and split them apart afterwards.

Input parameters

Parameter	Type	Default	Description
instanceUrls	array	–	Home pages of the Bugzilla trackers to scrape, e.
product	string	–	Product to filter on, e.
searchText	string	–	Runs the tracker's own quick search, e.
bugStatus	string	any	Restrict to one status.
maxPagesPerInstance	integer	4	How many result pages to walk for each instance.
maxItems	integer	500	Stop after this many bugs.
maxConcurrency	integer	2	Parallel requests.
proxyConfiguration	object	{"useApifyProxy": true}	Proxy used to fetch pages.

Tips for best results

• Paste the tracker's home page, e.g. https://bugzilla.mozilla.org — the Actor appends the REST path.
• Bugzilla refuses a completely unfiltered query, so set at least a product, a status or a search term.
• Product is the most useful filter; Search text runs the tracker's own quick search.
• The API returns up to 500 bugs per page, so large exports need very few calls.
• isOpen is the flag to filter on — status names differ between installations.
• resolvedAt minus createdAt gives time-to-resolution without any extra lookups.
• Severity and priority labels are per-instance conventions, not a shared scale.
• duplicateOf is filled only for bugs closed as duplicates.
• Security-restricted bugs never appear — the Actor reads only what a logged-out visitor sees.
• Keep concurrency low; most Bugzilla instances are community-run servers.

Run outcomes: an empty result is not the same as a blocked run

A crawl that was refused and a query that genuinely has no matches both produce an empty dataset. Treating them as the same thing makes the output unusable for monitoring, so every run is classified and an unverified emptiness is never reported as success.

Outcome	Run status	Meaning
COMPLETED	Succeeded	Everything requested was fetched and rows were saved.
PARTIAL	Succeeded	Rows were saved, but some pages were unreachable.
EMPTY_RESULT	Succeeded	Pages were fetched and parsed and this query really has no bugs.
BLOCKED	Failed	Every request was refused with HTTP 403/429/503.
NOT_FOUND	Failed	The source answered 404; check the address or filters.
FETCH_FAILED	Failed	Nothing could be fetched for transport reasons.
INCOMPLETE_NO_ROWS	Failed	Pages were skipped and nothing was saved, so an empty result cannot be trusted.

The rule behind the table: a run that fetched nothing can never finish as Succeeded. Each run also writes a SUMMARY record to the key-value store with pages requested, pages fetched, pages skipped, HTTP request and retry counts, a per-status breakdown, transport errors and the termination reason — so the row count is always reconcilable with what the run actually did.

Integrations

Send results straight into the tools you already use: Google Sheets, Slack, Zapier, Make, Airtable or any Webhook. You can also schedule the Actor to run hourly, daily or weekly and have each run append to the same dataset, which is how you build a price or availability history rather than a one-off snapshot.

API usage

Run the Actor and collect results from any language. Replace <YOUR_TOKEN> with your Apify API token.

cURL

curl -X POST "https://api.apify.com/v2/acts/logiover~bugzilla-issue-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"bugStatus": "any", "instanceUrls": ["https://bugzilla.mozilla.org"], "maxItems": 2000, "maxPagesPerInstance": 4, "product": "Firefox", "searchText": ""}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/bugzilla-issue-scraper').call({"bugStatus": "any", "instanceUrls": ["https://bugzilla.mozilla.org"], "maxItems": 2000, "maxPagesPerInstance": 4, "product": "Firefox", "searchText": ""});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/bugzilla-issue-scraper').call(run_input={"bugStatus": "any", "instanceUrls": ["https://bugzilla.mozilla.org"], "maxItems": 2000, "maxPagesPerInstance": 4, "product": "Firefox", "searchText": ""})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Use with AI agents (MCP)

This Actor is available through the Apify MCP server, so an AI agent can call it as a tool. Point your agent at https://mcp.apify.com and it can run the Bugzilla Scraper on demand — for example: "Pull the first 500 bugs from Bugzilla and summarise what you find." The agent receives the same structured rows you would get from the UI.

FAQ

Do I need a Bugzilla account or API key?

No. The Actor reads publicly available data only. There is nothing to authenticate and no credentials to rotate.

How many bugs can I get in one run?

As many as the source exposes. Raise the page limit and Max items together; the run stops at whichever limit it reaches first.

Why did I get fewer rows than I asked for?

The source ran out of bugs. That is normal for narrow searches — broaden the query or add more targets to one run.

Are results de-duplicated?

Yes. Each bug is emitted once per run, even when it appears on several pages, so you are never billed twice for the same record.

Why are some fields empty?

Bugzilla does not publish every attribute for every bug. Empty means the source did not supply it, not that extraction failed.

What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two. Raise Max concurrency carefully — the source rate-limits aggressive crawling.

Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset for time-series analysis.

Does it work behind a proxy?

It uses Apify Proxy automatically. You can switch groups or supply your own proxies in Proxy configuration.

How often does the data change?

Bugzilla updates continuously. Re-run whenever you need current data; the Actor always reads the live source, never a cache.

Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

What if the source changes its format?

Open an issue on the Issues tab and it gets fixed. The Actor is actively maintained.

Is it legal?

This Actor reads only publicly available data from Bugzilla — the same content any visitor or client sees without logging in. It does not bypass authentication, does not collect private data and does not attempt to defeat access controls. You are responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved. Scraping public data is generally lawful in the EU and the US, but the responsibility for the downstream use of that data sits with you.

Related scrapers

• GitHub Repository Scraper — Repository metadata
• Gitea & Forgejo Scraper — Self-hosted forges
• CVE Advisory Monitor — Disclosed vulnerabilities
• Stack Exchange Scraper — Developer Q&A