Help & Documentation

Offline-first guidance for safe gear lists.

Feedback & Support

Bug reports and feature requests via the Help panel's Support tab

The Support tab inside the Help panel sends bug reports and feature requests. It auto-attaches system info and recent in-app error logs, and accepts up to 2 screenshots. The 'Was this helpful?' thumbs at the bottom of each help article is a separate, anonymous signal — quick to send but not a way to reach support.

Where to Send a Report

Two separate channels — pick the one that fits your message.

Help panel → Support tab
The structured form for bug reports and feature requests. Subject, description, optional steps / use case, up to 2 screenshots, auto-attached system info and error logs.
Article thumbs (👍 / 👎)
Anonymous 'was this helpful?' signal at the bottom of every help article. Useful for low-effort signal — not a way to reach a human.
Tips
  • Sidebar → 'Help' opens the Help panel; the Support tab is one of its top-level tabs.
  • There is no floating 'Feedback' button in the corner of the app — the Support tab is the entry point.

Contact Form

A public form for everything that is not a bug report: questions, billing, privacy, legal.

  • The form is at /contact (German: /kontakt) and works without an account. The Imprint links to it under Contact.
  • Enter your name, your email address and your message; a topic is optional. Your message reaches the team as an email, and the answer comes by email to the address you entered.
  • The form stores nothing and you do not get a copy by email. The page shows 'Message sent' once the message has been handed over.
Tips
  • If the page says the message was not sent, write to support@cine-power-planner.com instead. Nothing is queued.
  • There is a limit of a few messages per hour. After 'Too many messages' wait an hour or use the email address.
  • Found a bug? Use the Help panel's Support tab: it attaches the system details that make a bug reproducible.
  • To report illegal content, use /report-content, not this form.

Bug Report vs. Feature Request

The form has two report types. They ask for different fields because they need different information.

Bug Report
Subject, description, and optional steps-to-reproduce. Best used when something is broken or behaves unexpectedly.
Feature Request
Subject, description, optional use-case and friction-points fields. Best used to propose a new capability or workflow improvement.
Tips
  • Steps-to-reproduce on a bug report are the single biggest factor in how quickly it gets fixed.
  • Use-case + friction-points on a feature request give context the title alone can't — fill them in even briefly.

Screenshots & Auto-Attached Data

The form attaches a few things automatically. Look them over before submitting.

  • Screenshots: up to 2 images, PNG or JPEG, max 5 MB each. Compressed to 1200 px on the long edge before upload.
  • System info: browser, OS, app version, screen size, online/offline state — auto-collected and visible in the form.
  • Recent error logs: the last 50 in-app error entries (getErrorReports()) are attached. Expand the 'Show recent logs' section to review what's included.
  • Nothing else is included automatically — no project data, no gear lists, no contacts.
Tips
  • Before attaching a screenshot, double-check it doesn't show sensitive client or production data.
  • If the bug only shows up with one specific project, mention the project name in the description — the project itself is not uploaded.

Writing a Useful Bug Report

What the form is trying to capture — and how to fill it in so it lands well.

  • Describe expected vs. actual behavior in one sentence each. 'I expected X, but Y happened.'
  • Steps to reproduce starting from a known state (a fresh project, a specific screen).
  • Whether it's intermittent or happens every time.
  • Any recent action that seemed to trigger it (a sync, an import, a version update).
  • A screenshot of the bad state if it's visual.
Example shape of a bug report

A structure that maps cleanly to the form fields:

  1. Subject: 'PDF export cuts off bottom row of gear list'
  2. Steps: '1. Create a project with 40+ items. 2. Click Export → PDF. 3. Open the generated PDF.'
  3. Expected: 'All items visible on the PDF.'
  4. Actual: 'Last 3 items are cut off on page 2.'
  5. Screenshot attached showing the truncated page.
Common Pitfalls
  • Submitting 'doesn't work' with no further detail — the form has space for steps; use it.
  • Forgetting which project / surface the bug happened on.
  • Not mentioning whether the issue is reproducible or intermittent — these get triaged very differently.

Privacy

What gets uploaded when you press Send.

  • Your typed text, attached screenshots, the auto-collected system info, and the last 50 in-app error log entries.
  • No project data, gear lists, contacts, or files are sent without an explicit action.
  • Transmission is over HTTPS.
  • The form lets you review every attached piece (including the error logs) before submitting — nothing is sent silently.
Tips
  • Blur or crop screenshots that might include client names, contact info, or rates.
  • For genuinely sensitive issues (security, account access), email support directly instead of using the in-app form.

Bug reports and feature requests are read. You may not get a per-message reply, but they shape the next versions — watch What's New for results.

Was this helpful?

Related Topics

See also