A well-written post gets faster, better answers. A vague one gets ignored or turns into a slow back-and-forth. This guide covers both Bug Reports and Feature Requests.

Before You Post

Update Stage Traxx: Apple's auto-update is slow. Go to the App Store and force the update. Check the latest version at Release Notes.
Check the Documentation: Many questions and feature requests are already covered: stagetraxx.com/docs/v4
Search the Forums: Someone may have already reported your issue or suggested your idea: support.stagetraxx.com. You can also check In Progress bugs and Planned features.
Do not double post: Do not post the same issue or idea multiple times.

Bug Reports

Tags: Support + Stage Traxx or Stage Cue + iOS and/or macOS. Only use the Bug tag if Stage Traxx is doing something wrong based on documented behaviour, not just because you disagree with how something works.

Include in your post:

Stage Traxx Version/Build: (e.g. ST 4.0.7)
Device & OS Version: (e.g. iPad 9th Gen, iOS 18.5)
Issue Description: What is the problem? Be specific. Stick to facts, avoid "it doesn't work" or "is broken."
Steps to Reproduce: The exact steps someone else would follow to see the same issue. Problems that can't be reproduced are much harder to fix.
Expected Behaviour: What should happen?
Actual Behaviour: What happens instead?
Attachments: Screenshots, videos, or support logs (via Settings > Create Support Email) are extremely helpful. Only images can be uploaded in the forum use something like https://imgur.com if you want to share a short video clip.

One issue per post. Don't combine unrelated problems, and don't hijack someone else's thread. Start your own and link to theirs if related.

Feature Requests

Tags: Feature Requests + Stage Traxx or Stage Cue + iOS and/or macOS.

Include in your post:

Stage Traxx Version/Build: (e.g. ST 4.0.7)
Device & OS Version: (e.g. iPad 9th Gen, iOS 18.5)
Current Limitation: What are you trying to do, and what's in the way?
Proposed Feature: Describe what you'd like to see.
Benefit / Impact: Why is this helpful? How does it improve the workflow?
Implementation Idea (optional): Any thoughts on how it could work? Mock-ups or annotated screenshots are a huge bonus.

General Tips

Don't post frustrated. Take a breath, compose your thoughts, then write. Frustrated posts tend to be heavy on emotion and light on the facts people need to help you.
Be clear and concise. A well-structured post respects everyone's time, yours included.
The community helps voluntarily. Making your post easy to understand is the single best thing you can do to get a fast, accurate response.