How to report a bug – step by step
PaperOffice greatly appreciates your assistance and under certain circumstances you will receive a one-time bug bounty of up to 500,- Euro
These 3 rules are mandatory – without them your bug report will not be processed:
1. Always use the latest PaperOffice release – download it fresh for every installation.
2. Reproduce the bug on a freshly installed, clean Windows machine (PC or VM) – no antivirus, no third-party software.
3. Record the entire process as an uncut video – from installation all the way to the bug.
Step 1: Prepare a clean Windows machine
Install a fresh, clean Windows (physical PC or virtual machine). No third-party software, no antivirus scanner, no third-party firewall – nothing that could interfere with the process. This is the only way to isolate the bug.
Step 2: Download the latest release
Download the latest PaperOffice release fresh from our website. Never use old installation files. Bug reports based on outdated versions will not be processed.
Step 3: Start the video recording
Start the screen recording before the installation. Windows 10 and 11 include a built-in screen recorder (Windows key + G).
- The video must be uncut: installation -> program start -> login -> bug.
- Sped-up sections are allowed, cuts are not. Edited videos will not be accepted.
- Log in with the licensed user account.
Step 4: Reproduce the bug with a local database
Create a new, empty, local database and reproduce the bug.
External database servers: no support. We cannot process bugs that only occur with a self-hosted MariaDB/MySQL server or NAS – configuration and hardware are outside our control. Always reproduce using a local database.
Step 5: Document the steps in writing
Describe the reproduction in the form "1) ..., 2) ..., 3) ..." and clearly separate observation from expectation:
| Information | Example |
|---|---|
| Reproducibility: always, occasionally, or not at all? | I can reproduce the bug as follows: |
| Exact click sequence in PaperOffice |
1. Start PaperOffice by double-clicking the desktop icon. 2. Click Continue in the login window. 3. ... |
| Expected vs. actual result |
Expected result: The interface finishes loading and displays the daily briefing. Actual result: The loading window keeps running indefinitely and the program stops responding. |
Step 6: Rate the impact
Blocker / Showstopper: No task can be performed.
Critical: Unexpected application termination, data loss.
Major: Major loss of functionality.
Medium: Medium loss of functionality.
Minor: Minor user interface improvements.
Step 7: Provide system information
- Operating system, processor, memory, hard drive of the test machine (or device manufacturer and model)
- Administrator rights or restricted rights?
- Optional: suggested fix, if you have one
Step 8: Create a ticket
Create a ticket in the PaperOffice comdesk with the bug report, the uncut video, and any affected files.
Include affected files whenever possible – hide confidential data beforehand. Provide large files (e.g. the video) online and include the download link in the ticket.
IMPORTANT: Without complete information for steps 1–8 your bug report cannot be processed.