Alpaca Issue Tracker vs Breadbugger

Alpaca Issue Tracker is a powerful yet simple issue tracking system that lives inside your WordPress admin. Built with the WordPress philosophy in mind, it provides a Trello-like kanban board interface for managing bugs, feature requests, and project tasks. Key Features Kanban Board Interface – Drag-and-drop issues between and within fully customizable status columns Automatic Context Capture – Browser info, page context, and technical details are saved with each bug report submitted from the front end Built for WordPress – Uses native WordPress components, post types, taxonomies and database tables Extensibility – Developers can add custom functions and integrations via conventional WordPress actions & filters Respects User Permissions – Integrates with WordPress user roles and capabilities Screenshot Capture – See exactly what the user saw, captured and processed locally within the browser Comment and Activity Thread – A unified view of each issue’s progress, supporting attachment uploads and user mentions Priority Management – Flag high-priority items and set deadlines Assignee System – Assign issues and checklist items to team members Email Notifications – Instant or daily digest email notifications for the issues you care about Translation Ready – Fully localized and ready for translation into any language (including RTL support) No Artificial Limitations – Use on as many sites, with as many users, issues, attachments and interactions as you need Perfect For Freelance developers managing client sites Small agencies tracking bugs and feature requests Development teams needing lightweight project management Clients performing QA on a new site Account managers responsible for rolling retainer contracts Enterprises and government bodies needing extra reassurance on hosting How It Works Clients don’t have the time or knowledge to provide detailed technical reports when they spot a problem. But developers can’t do their job without that detail. Alpaca Issue Tracker solves this by automatically capturing all the technical context WordPress already knows about each page request. When a user reports an issue via the Alpaca Issue Tracker front-end toolbar, the plugin silently captures: – A screenshot of what the user can see – Browser and device information – Current page URL and template – Queried object details and HTTP headers – Any JavaScript errors This gives developers everything they need to reproduce and fix issues quickly, with zero burden on the client. Issues can also be created on the admin side, meaning Alpaca Issue Tracker can also be used as a complete project management system, to plan new features or track internal tasks. Third-Party Libraries Alpaca Issue Tracker includes runtime copies or bundled output from the following GPL-compatible libraries: Bowser – MIT license – https://github.com/bowser-js/bowser DOMPurify – MPL-2.0 option from (MPL-2.0 OR Apache-2.0) – https://github.com/cure53/DOMPurify Marked – MIT license – https://marked.js.org/ PrismJS – MIT license – https://prismjs.com/ PropTypes – MIT license – https://github.com/facebook/prop-types SnapDOM – MIT license – https://github.com/zumerlab/snapdom Recommended Plugins Alpaca Issue Tracker uses user images throughout its interface, for extra humanity. We recommend Simple Local Avatars as a reliable solution for processing and hosting photos of your users without using an external service. Development Source code and build configuration are available at: https://github.com/rareview/alpaca-issue-tracker Building from Source Clone the repository Run npm install Run npm run lint Run npm run build Run npm run zip to create a distributable package The distributed plugin includes compiled JavaScript and CSS assets. The source files, dependency manifests, and build instructions are available in the repository above. Composer dependencies are used for development tooling and coding standards checks. Privacy Policy Alpaca Issue Tracker does not collect or transmit any data outside of your WordPress installation. All issue data, screenshots, and technical information are captured and stored locally in your WordPress database and/or filesystem. Credits Developed by Rareview®

Breadbugger is a bug tracking tool built for the pre-launch phase of a WordPress site — the moment when designers, QA, developers and clients walk through the site looking for issues before go-live. Three complementary surfaces: On-page floating widget — open the widget with a configurable keyboard shortcut, “pin” reports directly to the HTML element they refer to, attach screenshots captured on-the-fly from the browser. Clean admin list — manage every report from a compact full-screen view: filter by status, priority, author; sort manually with drag & drop; reply with inline notes. REST API for external clients — app-password gated endpoints to integrate your bug tracker with CLIs, AI coding assistants, or custom scripts. Key features Stable pin selectors — element selector built via a cascade: data-breadbugger-name (opt-in dev), then stable id, then semantic class, then positional CSS. Pins survive refactors. Configurable hotkey — press the keys to set your preferred combo, with browser/OS collision validation. Reporter / manager role model — assign who can open reports (reporter) and who can manage them all (manager) via custom capabilities on any WordPress role. Author filter + configurable visibility — managers can see and filter by author; reporters can optionally see only their own bugs. In-browser screenshots — automatic capture via getDisplayMedia (HTML2Canvas-Pro as a fallback for modern CSS like oklch / color-mix). Internationalized — Italian source, .po / .mo translations, .pot template ready for any language. Built-in feedback channel — settings form to send bug reports / feature requests / questions to the author via wp_mail. Branded email notifications — HTML emails for @mentions in notes and (optional) for new bugs and resolved bugs, with per-recipient frequency: all events, accorpate (timeout-based), daily digest, weekly digest, or none. Use case Client site pre-go-live: 5-10 people testing in parallel. Each one loads the site, opens the widget with a shortcut, pins the issue directly on the affected element. The PM / dev watches the admin list, sorts by priority, assigns fixes, marks resolved. Standalone. No external SaaS required. No data sent to third-party servers. Your bugs stay in your database.