Skip to content

馃悰 Incorrect Dashboard Display for Cancelled Offline Payment Orders#1317

Description

@justusweigmann

Bug Report: Incorrect Dashboard Display for Cancelled Offline Payment Orders

Describe the bug
When an order with an 'Offline' payment method is cancelled, it is not correctly reflected in the event dashboard statistics. Specifically, these orders are not automatically fully handled regarding cancellations/refunds, and the dashboard metrics (e.g., revenue, total refunded, etc.) do not accurately represent these cancelled offline transactions.

To Reproduce
Steps to reproduce the behavior:

  1. Create or navigate to an event in the Hi.Events dashboard.
  2. Locate an order that was processed via an 'Offline' payment method.
  3. Attempt to cancel or void this order.
  4. Observe that the dashboard metrics are not updated to reflect the cancellation/refund status correctly, or that the system does not allow for a proper refund indication for these offline payments.

Expected behavior
Cancelled orders, including those with 'Offline' payment methods, should be properly accounted for in the dashboard metrics. The system should allow the user to properly mark these as refunded or ensure they are excluded/adjusted in the revenue reporting, ensuring the data visualized in the dashboard matches the actual state of the orders.

Screenshots

Image Image

Desktop (please complete the following information):

  • OS: macOS (aarch64)
  • Browser: Firefox
  • Version: 153.0.4

Hi.Events Version and platform

  • Version: v1.11.1-beta
  • Platform: Docker (all-in-one)

Additional context
The issue is specifically problematic for offline payments because they seem to lack the automated cancellation/refund flow that online payment providers might have, leading to discrepancies in the reporting dashboard.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions