Reporting Bugs on Odoo Support Page – What’s the Right Way?

[vihanrichard]

Hi everyone,
I’ve been navigating the Odoo support portal at odoo.com/help while managing a few active projects and noticed some usability issues—broken links, slow-loading components, and occasional form errors. It made me wonder: where’s the official place to report such bugs? I didn’t find an obvious “Report a Bug” button or public issue tracker for the support interface itself.

For those of us offering or using Odoo Maintenance Services or Odoo Support Services, a smooth and error-free support experience is critical. Whether you’re trying to raise a ticket, check a case status, or review documentation, even small bugs can disrupt workflows.

At Webkul, we frequently deal with Odoo support when deploying or maintaining large Odoo setups for our clients. Timely bug reporting helps us plan maintenance cycles more accurately and reduce overall support turnaround time. But when it comes to the official Odoo website (especially help pages), the process for feedback isn’t always straightforward.

Has anyone here submitted bugs directly to Odoo related to their support portal? Did you get a response? Should we post in the Odoo forums, send emails to their support team, or is there an internal feedback mechanism I may have missed?

Also, it would be helpful if Odoo allowed logged-in users to submit UI/UX feedback right from the page in question. Something like a GitHub-style tracker for non-core issues would go a long way.

Open to suggestions and hearing your experiences!

[bloomagency]

Great question—reporting bugs the right way on the Odoo Support page really matters because it directly affects how fast (and accurately) the issue gets resolved.

From experience working with ERP systems like Odoo, the biggest issue is not that bugs aren’t reported, but that they are often reported without enough context for the support team or developers to reproduce them.

Here’s a practical breakdown of the “right way” to report bugs on the Odoo Support page:

---

1. First, confirm it’s actually a bug
Before submitting a ticket, try to separate:

• Bug → Something that worked before or should work based on documentation but fails
  
• Configuration issue → Missing setup, wrong permissions, or misconfiguration
  
• Custom module issue → Problem caused by third-party or custom development
  
• User error → Incorrect usage of the system
  

A lot of tickets get delayed because they are actually configuration-related rather than core bugs.

---

2. Provide a clear, descriptive title
Avoid vague titles like:

• “Something not working”
  
• “Error in Odoo”
  
• “Issue in sales module”
  

Instead, be specific:

• “Invoice validation fails when tax is applied in multi-currency setup”
  
• “Kanban view crashes when filtering by custom field in CRM module”
  

A precise title helps support teams route the issue faster.

---

3. Always include steps to reproduce
This is the most important part. Write it like a recipe:

• Step 1: Go to Sales → Orders
  
• Step 2: Create a new quotation
  
• Step 3: Add product with tax X
  
• Step 4: Click confirm
  
• Step 5: Error appears
  

If the issue cannot be reproduced, it usually cannot be fixed.

---

4. Attach logs, screenshots, or screen recordings
Visual proof saves a lot of time:

• Screenshot of the error message
  
• Full traceback from developer mode
  
• Screen recording (if workflow-related)
  

If you're on Odoo.sh or a hosted environment, include relevant server logs if possible.

---

5. Mention environment details
Always include:

• Odoo version (e.g., 16.0, 17.0)
  
• Hosting type (Odoo Online / Odoo.sh / On-premise)
  
• Browser and device (if UI-related issue)
  
• Installed custom modules (if any)
  

Many bugs are version-specific, so this is critical.

---

6. Include expected vs actual behavior
This helps clarify the issue quickly:

• Expected: System should allow invoice validation with multiple taxes
  
• Actual: System throws validation error and blocks posting
  

This removes ambiguity.

---

7. Check for duplicates before submitting
Odoo’s issue tracker often already has similar reports. Searching first can:

• Save time
  
• Let you follow existing threads
  
• Increase visibility on known bugs
  

---

8. Be polite and structured in communication
Support teams prioritize tickets that are:

• Clear
  
• Complete
  
• Easy to reproduce
  

A well-written report is often resolved faster than a rushed one, even if the bug itself is the same.

---

Final thought

Good bug reporting is basically good communication. The more reproducible and structured your report is, the faster the fix cycle becomes.
If anyone here has submitted Odoo bug reports before, it would be interesting to know—what kind of issues got resolved quickly and which ones took longer than expected?