GitHub Helpdesk Bug Sync

Key features

• Systray bug button on every backend screen — no need to open Helpdesk first
• Screenshot capture of the current tab plus optional extra images
• Structured fields: what you were doing, expected result, actual result
• Automatic page URL and configurable ticket priority
• Creates a Helpdesk ticket on your chosen team
• Send to Git — create a GitHub issue with labels and milestone

Typical use

QA, consultants, or power users who spot a regression while working in Sales, Inventory, Contacts, or any other app and want support and development on the same ticket — without copying URLs into email or Slack.

Dependencies

Helpdesk (helpdesk) — Odoo Enterprise. Also web, mail, base_setup.

GitHub sync is optional; bug reports still work with Helpdesk only.

Connect GitHub

Open Settings → Bug Tracker. Paste a Personal Access Token (ghp_... or github_pat_...) with repo scope; after save the field is cleared and a green badge confirms storage.

Set the API URL (github.com or GitHub Enterprise), owner, repository, and comma-separated default labels (they must already exist on the repo).

Use Test connection to verify credentials, then Sync milestones to pull milestones into Odoo for assignment on tickets.

Also choose the Helpdesk team where new bug reports are created and optional defaults (priority, assignee).

Report from anywhere

A dedicated bug icon sits in the top bar on every backend view. Click it while you reproduce the problem — for example on Contacts, Sales, or Inventory — without leaving the screen where the bug appears.

Your browser prompts you to share the current tab; the wizard then opens with the page URL already filled in.

Structured bug report

The Report an Issue dialog captures a clear title, priority (Low / Medium / High / Urgent), and the read-only page URL.

Three guided sections — What were you doing?, Expected result, and Actual result — give developers reproducible steps instead of a single vague paragraph. Add a free-form description and the captured screenshot (plus optional extra images).

Submit creates the Helpdesk ticket on your configured team and attaches screenshots to the chatter.

Helpdesk ticket with context

Each report becomes a standard Helpdesk ticket on your bug team, with customer, priority, and pipeline stages (New, In Progress, On Hold, …).

A dedicated Bug report block stores the page URL and the three structured answers so agents and developers see the same context as the reporter.

When GitHub is configured, click Send to Git to open an issue in your repository. The ticket keeps the issue number and URL; a second push is blocked once synced.

Issue on GitHub

The new issue appears in your repository with the ticket title and body, plus the default labels from settings (for example bug and odoo) and an optional milestone chosen on the ticket.

Developers stay in their usual GitHub workflow — triage, assign, and close — while support keeps tracking the same case in Helpdesk.