The Feedback entry on the dashboard exists so the team can prioritize real pain. The best reports are boring: clear steps, one problem per report, and evidence that removes guesswork.
Bug reports that work
What you clicked and in what order.
What you expected versus what happened—one sentence each.
Browser and OS version; approximate time for transient errors.
Screenshots or screen recordings for UI state issues.
Whether it reproduces in a fresh session or incognito—helps isolate extensions.
Feature requests that work
Problem first: what workflow is blocked?
Proposed solution second—maybe the team has a better design.
Who benefits: solo creator, team, admin—prioritization differs.
What not to do
Avoid bundling five issues in one ticket—each gets lost. Avoid vague (“AI is bad”) without an example prompt and outcome. Avoid sharing secrets in screenshots; redact tokens.
Guides and blog
Search guides before filing—often a workflow already exists. The blog covers releases; pair it with Feedback when a new feature behaves unexpectedly.