Alpaca Issue Tracker vs PSBDx Smart Report Management

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®

PSBDx Smart Report Management turns any WordPress site into a lightweight support desk. Customers report a problem — with an order, a product, a course, or anything else — through a fast AJAX modal that never reloads the page, and every submission lands in a clean, organized admin inbox your team actually enjoys working from. No support-ticket plugin bloat, no separate helpdesk to learn, no per-agent pricing. Just a focused, fast, genuinely useful report and complaint management system that plugs straight into WooCommerce and LearnPress — and, when you want it, hands the busywork of sorting and prioritizing incoming reports to AI. Why site owners choose it It’s instant. Reports submit over AJAX with no page reload, so customers actually finish the form instead of abandoning it. It sorts itself. Turn on AI-assisted classification and every new report gets a suggested category and priority (Low / Medium / High) automatically — you triage a full inbox in minutes, not hours. It gives customers a reference. Every report gets its own unique, human-readable Ticket ID, so a customer can follow up by email or phone and your team can find the exact report instantly. It already knows your store. Reports from a WooCommerce order page auto-link to that order; reports from LearnPress courses, lessons, and quizzes are just as seamless. It fits your workflow, not the other way around. Custom statuses, custom categories, per-form rate limiting, captcha, and a drag-and-drop form builder mean the plugin adapts to how you already work. Key Features AJAX-powered modal report form — no page reload, works anywhere via shortcode Optional AI-assisted triage (WordPress 7.0+): automatically suggests a category and priority for every new report using the built-in WordPress AI Client — gracefully disabled with no impact on the rest of the plugin if you’re on an older WordPress version or haven’t connected a provider “Summarize with AI” on the report edit screen — a plain-language explanation of what the customer is actually reporting, for reports that are long or vaguely worded AI Response Log: a rolling 3-hour audit trail of every AI request and response, so you can see exactly what the AI decided and why Unique, human-readable Ticket ID on every report — the customer’s reference for following up, shown in their confirmation and report history Admin-defined report Categories and Low/Medium/High Priority, settable manually or by AI, editable any time from the report edit screen Drag-and-drop Form Builder: ten field types (name, email, phone, text, paragraph, number, select, radio, checkboxes, captcha), fully reorderable, mobile-friendly Five built-in report statuses with colour-coded badges (Processing, Contacting, Waiting, Solved, Failed), plus unlimited custom statuses E-commerce order auto-link — reports from an order page are automatically linked to that order in the admin, HPOS-compatible Per-form cooldown / rate limiting enforced on both the frontend and the server, so the same user can’t spam a form Captcha support: Google reCAPTCHA, hCaptcha, and Cloudflare Turnstile Admin dashboard widget and admin-bar shortcut with live, at-a-glance unsolved-report counts Built-in FAQ builder with a [psbdx_faq] accordion shortcode for your own site’s visitors Mobile-first responsive design throughout, including iOS safe-area support and a touch-friendly admin experience LearnPress course, lesson, and quiz page support, alongside WooCommerce Reporter identity (name and email) collected server-side from the WordPress session — never editable by the user, so it can’t be spoofed Shortcodes: [psbdx_report id="X"], [psbdx_user_reports], and [psbdx_faq] Also configurable, per form Fully custom report reasons (comma-separated, “Other” always appended) Optional extra fields (e.g. Transaction ID, Coupon Code) Contact field with a required/optional toggle Show or hide the reporter identity card in the form Auto-display on all products/orders/courses, or assign a form per item Perfect for WooCommerce stores that need a fast, structured way for customers to report an order or product problem Online course sites (LearnPress) fielding student questions about a specific course, lesson, or quiz Any WordPress site that wants a lightweight complaint/report/support-ticket system without a heavyweight external helpdesk Shortcodes [psbdx_report id="X"] Display a report button and modal form. Replace X with the Report Form post ID shown in the Shortcode box. [psbdx_user_reports] Display a paginated table of the currently logged-in user’s report history, including their ticket IDs. [psbdx_faq] Display your admin-managed FAQ as a clean accordion, anywhere on your site. Developer Hooks For developers building integrations or extensions on top of this plugin. Report status changes Instead of polling the database, listen for these action hooks — they fire from the one place in the plugin that ever writes a report’s status, so they’re guaranteed to fire exactly once per real change: psbdx_srm_report_status_changed( $report_id, $old_status, $new_status, $context ) Fires for every status change, whatever the new status is. psbdx_srm_report_status_changed_to_{$new_status}( $report_id, $old_status, $context ) Fires only for one specific new status (status run through sanitize_key()), e.g. psbdx_srm_report_status_changed_to_solved. Use this instead of the generic hook if you only care about one transition. $context is an associative array: report_id (int) — same as the first hook argument, included for convenience. ticket_id (string) — the report’s human-readable ticket ID. submitter_id (int) — numeric WP user ID of whoever filed the report, or 0 for a guest. submitter_email (string) — the reporter’s email address, if one was collected. old_status (string|null) — the previous status key, or null if this report never had one before (i.e. this is the very first status it’s ever had, from a brand-new submission). new_status (string) — the new status key. changed_by (int) — numeric WP user ID of whoever triggered the change (typically the logged-in admin editing the report), or 0 for a guest’s own submission or an automated process. updated_at (string) — MySQL datetime in GMT/UTC. updated_at_local (string) — MySQL datetime in the site’s local timezone. source (string) — where the change came from: submission (a brand-new report), admin (the report edit screen), or another value a specific integration may pass. Example: add_action( 'psbdx_srm_report_status_changed', function( $report_id, $old_status, $new_status, $context ) { error_log( sprintf( 'Ticket %s (user #%d): %s -> %s', $context['ticket_id'], $context['submitter_id'], $context['old_status'] ?? '(new)', $new_status ) ); }, 10, 4 ); Note: bulk/maintenance operations that write status directly to the database (CSV import, and the Repair & Reset page’s “fix invalid status values” tool) intentionally do not fire these hooks, since they’re bulk restores rather than individual live status changes. Upcoming Features The following features are planned for future releases: Email Notifications — Notify the admin on new submissions, and send a confirmation email to the reporter. Status Change Emails — Email the reporter automatically when their report status is updated. CSV Export — Export all report logs as a CSV file from the admin screen. File / Screenshot Attachment — Let users attach a screenshot or file to their report. (Added ✅) Internal Admin Notes — Private notes on each report log, visible only to admins. Report Categories / Tags — Organise reports with admin-defined categories for easier filtering. (Added ✅) Guest Email Verification — Allow non-logged-in users to submit with email verification before saving. (Added ✅) Duplicate Detection — Alert admins when a new report closely matches an existing open one. (Added ✅) Report Priority Levels — Assign Low / Medium / High priority to reports, manually or via AI. (Added ✅) REST API Endpoints — Query and manage reports programmatically via the WordPress REST API. AI Knowledgebase Suggestions — Recommend existing help-article answers to reporters based on their report content. (Settings → AI → Knowledgebase — coming soon)