Guide: Creating a Bug Report

1. Purpose and Overview

If an error occurs in OptionsApp or unexpected behavior is observed, you can send an error report to the development team using the integrated Bug-Report function.

A Bug-Report contains not only the error description but also technical information such as logs and configuration data from the current session. This allows the development team to understand exactly under which conditions the error occurred.

This enables significantly faster analysis and resolution of potential issues.

2. Location of the Bug-Report Function in the User Interface

The Bug-Report function is available in all areas of OptionsApp.

It is located in the upper right bar of the user interface and is marked with a bug icon.

The function can be used independently of the current area of the app, for example from:

• Dashboard
• Configurations
• Evaluations
• Settings

Clicking on the bug icon opens the dialog for creating a Bug-Report.

3. Creating a Bug-Report

After opening the Bug-Report dialog, you need to enter some information about the problem that occurred.

Bug-Report Title

In the Title field, enter a brief summary of the problem.

Examples:

• "Trade was not opened"
• "Exit Condition was not triggered"
• "Wrong Strike displayed in Dashboard"

The title is only for quick categorization of the problem.

Problem Description

In the Description field, describe the problem in as much detail as possible.

A detailed description helps the development team understand the situation exactly. The following information is particularly helpful:

• What exactly happened?
• What was expected?
• When did the problem occur?
• What steps were performed beforehand?

4. Specifying Affected Trades

If the problem relates to a specific trade, you should provide as detailed information as possible about that trade.

Helpful information includes, for example:

• Time of trade opening or expected entry
• Time of closing
• affected strategy

Particularly helpful is the Trade Number.

This is displayed in OptionsApp in the Dashboard and in the Evaluations area directly after the trade name in square brackets.

The Trade Number greatly facilitates targeted analysis in the system.

5. Attaching Additional Files

Optionally, you can add additional files to the Bug-Report.

This can be particularly helpful if you have visual information about the error situation.

Typical examples are:

• Screenshots from OptionsApp
• Screenshots from Trader Workstation (TWS)
• Screenshots from backtesting tools like Option Omega
• other relevant files or documentation

These files can be uploaded directly in the Bug-Report dialog.

6. Sending the Bug-Report

After all information has been entered, there are two options for saving or sending the Bug-Report.

Send Report (recommended)

With the Send Report option, the Bug-Report is sent directly to the OptionsApp team.

This is the recommended approach since the report enters the support system immediately and can be analyzed.

7. Processing by the Support Team

After sending, the Bug-Report is analyzed by the support and development team.

Both the error description and the transmitted technical data are reviewed to identify the cause of the problem.

As a rule, you will receive feedback on the reported problem within a few days.