Channels

A channel is a bucket that reports are sorted into — by default, by what kind of feedback they are. Each report carries a channelKey that says which channel it belongs to.

Seeded channels

When you create a project, Patchrooms automatically creates three starter channels:

Name	Key
Bugs	bug
Ideas	feature
Alpha feedback	alpha-feedback

The new project’s default channel is set to bug, so a report that isn’t routed anywhere else lands in Bugs.

You can rename channels, change their color, archive the ones you don’t use, and add your own. A channel’s key is unique within its project — two channels in the same project can’t share a key.

Note

Renaming a channel changes its display name, not its key. The key is the stable identifier that reports reference, so existing reports keep pointing at the right channel even after a rename.

channelKey is the canonical field

Every report stores a channelKey — the key of the channel it was filed into. This is the single source of truth for which channel a report belongs to. You’ll see channelKey in:

• the dashboard, when you filter reports by channel,
• the export ZIP, where you can scope the download to one channel,
• the report payload itself.

How a report picks its channel

A room can choose its channel before sending. The SDK lets you set the active channel for the widget, and the embedded widget reflects the active channel as the reporter works. If nothing sets a channel, the report falls back to the project’s default channel (bug on a fresh project).

Caution

Channels are scoped to a single project. A bug channel in one project is a completely separate channel from a bug channel in another — they only share a name by convention.