What should beta testers report first?

Short answer

Beta testers should prioritize access problems, save failures, broken buttons, confusing workflows, mobile layout issues, and anything that blocks completing a real event.

Learn moreWhat information should I include in a support request?Why am I missing a button or page?

Highest priority

  • Login or magic-link problems
  • Events, planning cards, CRM rows, forms, or songs not saving
  • Buttons that appear clickable but do nothing
  • Critical errors, blank pages, or endless loading
  • Mobile screens where controls are hidden behind the phone safe area
Learn moreWhy am I missing a button or page?

Medium priority

  • Confusing labels
  • Missing help text
  • Dark-mode contrast issues
  • Unexpected page jumps or scroll behavior
  • Features that work but feel hard to understand
Learn moreWhat should I do if a page looks wrong in dark mode?Why am I missing a button or page?

Lower priority

  • Small wording preferences
  • Purely visual polish that does not block the workflow
  • Ideas for future features that do not affect the beta workflow.

Related articles

What information should I include in a support request?Learn moreWhy am I missing a button or page?Learn moreWhat should I do if a page looks wrong in dark mode?Learn more

Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.