How to report a bug
What it is for
This chapter covers what to check before reporting a bug in Doubleros and what to put in the report so it can be found and fixed quickly. The app has no built-in bug report form — send the report to your organization's admin or to Doubleros support through the contact you have agreed with Doubleros.
What to check before reporting
Most "bugs" in Doubleros have a simple cause. Try in this order:
- Read Frequently asked questions. The most common causes are a missing permission and a switched organization.
- Check the organization switcher at the top of the sidebar — are you in the right organization?
- Reload the page (Ctrl+R on Windows, Cmd+R on a Mac).
- Sign out and back in (avatar at the bottom of the sidebar → Logout).
- Try another browser or a private window — this tells an app problem from a browser problem (extensions, stale cached data).
- Read the message. A message saying what is missing (e.g. Name is required) is not a bug — just fill in the field.
What to put in the report
The more precise the report, the faster the fix. Include:
| Detail | Example |
|---|---|
| Where — menu path and screen | CRM → Clients → client detail |
| What you did — each click | clicked Save after changing the phone |
| What happened — the exact message | the message "Something went wrong" |
| What you expected | that the phone would be saved |
| When | date and approximate time |
| Who and where | organization name and the account e-mail you were signed in with |
| Browser and device | Chrome on Windows, Safari on iPhone |
| Does it repeat? | always / sometimes / happened once |
Attach a screenshot of the whole window — it often shows more than a description (current organization, the trail in the top bar, the message text).
What helps most
Steps that reliably reproduce the bug. Write them as numbered steps from opening the page to the error. If it only happens sometimes, say so — that is important information.
What does not belong in a report
- Passwords — never send them; support does not need them.
- API keys and secrets of payment gateways and integrations (e.g. Stripe Secret Key, Client secret). If you sent one by mistake, generate a new one at the provider.
- Customers' personal data beyond what is needed to find the record (an order number is usually enough).