2 changed files with 108 additions and 0 deletions
@ -0,0 +1,51 @@
|
||||
# OTB Billing Feedback Request Template |
||||
|
||||
Subject: OTB Billing test review request |
||||
|
||||
Hi, |
||||
|
||||
Thanks again for taking a look at OTB Billing. |
||||
|
||||
This is a test database and sandbox environment, so please feel free to: |
||||
- create test clients |
||||
- create services |
||||
- generate invoices |
||||
- record payments |
||||
- test exports and email functions |
||||
- try odd or edge-case workflows |
||||
|
||||
What I am looking for most: |
||||
- anything confusing |
||||
- anything that feels slower or harder than QuickBooks |
||||
- missing bookkeeping/accounting information |
||||
- reports or exports you would expect to see |
||||
- field names or screens that feel unclear |
||||
- anything that looks risky from a bookkeeping standpoint |
||||
|
||||
Suggested test flow: |
||||
1. Create a client |
||||
2. Create a service |
||||
3. Create an invoice |
||||
4. Send an invoice email |
||||
5. Record a payment |
||||
6. Export CSV / PDF / accounting package |
||||
7. Review revenue reporting |
||||
8. Try recurring billing / subscriptions if applicable |
||||
|
||||
Please send feedback in any format that is easiest for you, but this structure is especially helpful: |
||||
- Date |
||||
- Area of app |
||||
- What you expected |
||||
- What happened instead |
||||
- Suggested improvement |
||||
|
||||
Examples of useful feedback: |
||||
- "Invoice page should show client balance" |
||||
- "Payment screen needs clearer wording" |
||||
- "I expected a statement export" |
||||
- "This report is missing a field I need" |
||||
|
||||
Support / feedback email: |
||||
- support@outsidethebox.top |
||||
|
||||
Thanks — more eyes from people who know bookkeeping is exactly what helps make this useful. |
||||
@ -0,0 +1,57 @@
|
||||
# OTB Billing Test Feedback Log |
||||
|
||||
Use this file to collect tester feedback during sandbox / review cycles. |
||||
|
||||
## Instructions |
||||
|
||||
- Add one entry per issue, suggestion, or observation. |
||||
- Keep entries short and specific. |
||||
- Include screenshots or emailed notes separately if needed. |
||||
- Mark status as `open`, `reviewed`, `planned`, `fixed`, or `wontfix`. |
||||
|
||||
--- |
||||
|
||||
## Feedback Entry Template |
||||
|
||||
### Entry ID: FB-0001 |
||||
- Date: |
||||
- Tester: |
||||
- Area: |
||||
- clients |
||||
- services |
||||
- invoices |
||||
- payments |
||||
- subscriptions |
||||
- reports |
||||
- exports |
||||
- email |
||||
- settings |
||||
- installer |
||||
- other |
||||
- Type: |
||||
- bug |
||||
- usability |
||||
- bookkeeping |
||||
- accounting |
||||
- feature request |
||||
- reporting |
||||
- export |
||||
- wording |
||||
- other |
||||
- Severity: |
||||
- low |
||||
- medium |
||||
- high |
||||
- Summary: |
||||
- Steps to reproduce: |
||||
- Expected result: |
||||
- Actual result: |
||||
- Suggested change: |
||||
- Status: open |
||||
- Notes: |
||||
|
||||
--- |
||||
|
||||
## Active Feedback |
||||
|
||||
<!-- Copy the template above for each new item --> |
||||
Loading…
Reference in new issue