<p><hr> <h3>How to report a bug – step by step</h3> <p class="remark yellow mt-10"><span class="sub-alt-header">PaperOffice greatly appreciates your assistance and under certain circumstances you will receive a one-time bug bounty of up to 500,- Euro</span></p>
<div class="remark warning"> <p><b>These 3 rules are mandatory – without them your bug report will not be processed:</b></p> <p>
- Always use the <b>latest PaperOffice release</b> – download it fresh for every installation. <br>
- Reproduce the bug on a <b>freshly installed, clean Windows machine</b> (PC or VM) – no antivirus, no third-party software. <br>
- Record the entire process as an <b>uncut video</b> – from installation all the way to the bug. </p> </div>
<h3>Step 1: Prepare a clean Windows machine</h3> <p>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.</p>
<h3>Step 2: Download the latest release</h3> <p>Download the <b>latest PaperOffice release</b> fresh from our website. <b>Never</b> use old installation files. Bug reports based on outdated versions will not be processed.</p>
<h3>Step 3: Start the video recording</h3> <p>Start the screen recording <b>before</b> the installation. Windows 10 and 11 include a built-in screen recorder (Windows key + G).</p> <ul class="uk-list uk-list-bullet"> <li> The video must be <b>uncut</b>: installation -> program start -> login -> bug. </li> <li> Sped-up sections are allowed, cuts are not. Edited videos will not be accepted. </li> <li> Log in with the <b>licensed user account</b>. </li> </ul>
<h3>Step 4: Reproduce the bug with a local database</h3> <p>Create a new, empty, <b>local</b> database and reproduce the bug.</p> <div class="remark warning"> <p><b>External database servers: no support.</b> 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.</p> </div>
<h3>Step 5: Document the steps in writing</h3> <p>Describe the reproduction in the form "1) ..., 2) ..., 3) ..." and clearly separate observation from expectation:</p> <table class="table cell-border table-border"> <thead> <tr> <th> Information </th> <th> Example </th> </tr> </thead> <tbody> <tr> <td>Reproducibility: always, occasionally, or not at all?</td> <td>I can reproduce the bug as follows: </td> </tr> <tr> <td>Exact click sequence in PaperOffice</td> <td>
- Start PaperOffice by double-clicking the desktop icon. <br>
- Click Continue in the login window. <br>
- ... </td> </tr> <tr> <td>Expected vs. actual result</td> <td> <b>Expected result: </b>The interface finishes loading and displays the daily briefing. <br> <b>Actual result: </b>The loading window keeps running indefinitely and the program stops responding. </td> </tr> </tbody></table>
<h3>Step 6: Rate the impact</h3> <p> <b> Blocker / Showstopper: </b> No task can be performed. <br> <b> Critical: </b> Unexpected application termination, data loss. <br> <b> Major: </b> Major loss of functionality. <br> <b> Medium: </b> Medium loss of functionality. <br> <b> Minor: </b> Minor user interface improvements. </p>
<h3>Step 7: Provide system information</h3> <ul class="uk-list uk-list-bullet"> <li> Operating system, processor, memory, hard drive of the test machine (or device manufacturer and model) </li> <li> Administrator rights or restricted rights? </li> <li> Optional: suggested fix, if you have one </li> </ul>
<h3>Step 8: Create a ticket</h3> <p>Create a ticket in the PaperOffice comdesk with the bug report, the uncut video, and any affected files.</p> <p class="remark yellow"> <b> 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. </b> </p>
<p><b> IMPORTANT: Without complete information for steps 1–8 your bug report cannot be processed.</b></p></p>