Bug report, in depth
A bug report’s value is almost entirely in its context: what page, what action, what expected versus actual result. Reports collected without structure (“it doesn’t work”) generate a support round-trip before any engineer can act; reports that arrive with the page URL and a category already attached often skip straight to reproduction.
Bug reports also should not be public by default. They frequently contain account details, security-relevant behavior, or embarrassing specifics. Tools that push all feedback to a public board force users to either overshare or stay silent; a private path gets you the report with the details intact.
Putting it into practice
Give bugs their own category at capture so they never mix with feature ideas, and auto-attach page context. TellTide does both: the widget’s bug type carries the page URL into the private inbox, and the API accepts structured reproduction detail in a feedback_data field from native apps.