How can I prepare a useful Busabase issue report without sharing business data?

Thanks for asking. When something breaks on confidential data, a small invented mini-repro is usually enough for the Busabase team—as long as the shape of the problem stays the same.

What to keep unchanged

What to invent or omit

• Replace customer names, contract amounts, emails, phone numbers, internal codes with fake values (Acme Demo, 100.00, demo@example.com).
• Do not paste production exports that still contain real rows.
• Prefer a tiny Base with 2–5 sample records that still trigger the issue.

Suggested mini-repro pack

1. Create a throwaway Base that mirrors the failing schema (same field types / relations).
2. Enter invented rows that reproduce the steps.
3. Note the view filter formula / conditions in plain text.
4. Optionally export an empty template (structure only) if that helps hand-off—still without real data.
5. Attach UI screenshots of the failing step (blur anything sensitive).

*Diagram · keep schema shape; invent values*

*Diagram · keep field types; invent labels and values*

How to verify the report is useful

Before you send it, ask: *Could a stranger rebuild this Base from my notes and hit the same result?* If yes, the report is ready. If they would still need your production rows, invent more sample data instead of sharing confidential ones.

Boundaries

• Invented values are fine; wrong field types are not—don’t simplify a Relation into Text “to make it easier.”
• Permission / sharing bugs: describe roles and share settings without naming real people.
• If the bug only appears with a large volume, say so and give approximate counts—still without exporting the real table.

Happy to review a redacted outline of your fields/relations before you open a formal ticket.