Capture every bug, without leaving Slack
- Trigger
- 🐛:bug:
- Lands in
- Thread, plus the Issues board
- Setup
- 2 min
- Needs
- Via invited to the channel
Signup form rejects a plus sign in the email field
Filed by @calvin from this thread
- Severity
- high
- GitHub
- viably#412
- Attachments
- 1 screenshot
- Reported by
- @nadia
Title, description, and severity were written by AI from the thread. Without an AI key the raw text becomes the body instead.
- 1Someone reports a bug in chat
A teammate or a customer-support relay posts a message describing what went wrong. No special command is needed, because Viably reads it as the normal Slack message it is.
- 2React with a bug emoji
Add
:bug:,:beetle:, or:lady_beetle:as a reaction. Viably treats any of them as the “file this” signal. - 3Viably turns it into a structured issue
With @Via AI enabled, Viably reads the thread and infers a title, a longer description, and a severity. Without AI the raw text becomes the issue body, so nothing is lost either way.
- 4Posted back in Slack, and synced to GitHub
Viably replies in the thread with the captured issue card. If a GitHub repo is connected, a real GitHub issue is created with the same content and a permalink back to the Slack thread.
Three ways to file one
Three independent ways to file an issue. They all converge on the same workflow.
What the AI fills in for you
When @Via AI is configured with any provider key on the @Via AI config page, Viably uses the model to enrich each issue.
- Title, a concise summary ready for an issue tracker.
- Description, covering reproduction steps, expected against actual, and links from the thread.
- Severity, one of
low,medium,high, orcritical, based on impact cues in the text.
Viably falls back to the raw thread text as the issue body. The reaction-driven workflow still works, and the only thing you lose is the auto-extracted title and severity.
It lands in GitHub too
Connect a GitHub App from Powers → GitHub and pick the repos Viably is allowed to write to. After that, every issue created from Slack is mirrored to the default approved repo, or to one chosen at filing time.
- The GitHub issue body links back to the Slack thread for context.
- Severity becomes a label,
severity:high, so triage filters work without extra rules. - If sync fails, whether from a network blip or a repo somebody just deleted, Viably keeps the Slack-side issue and surfaces the error in the thread, so nothing is silently lost.
Screenshots come along
Image-bearing messages keep their attachments. Viably uploads them to private storage, signs URLs for the dashboard, and attaches a stable link to the GitHub issue.
The Issues page in the dashboard surfaces preview thumbnails for quick scanning, and clicking through opens the full image. Images are accessible only to authenticated workspace members.
React to the message with a bug emoji. Viably reads the thread, writes a title, description, and severity, posts the issue card back in the thread, and creates the matching GitHub issue if a repo is connected.
The workflow still works. Without AI the raw thread text becomes the issue body, so you lose the auto-written title and severity but never the bug report itself.
Yes, every synced issue carries a permalink to the Slack thread, so whoever picks the bug up can read the original report and the discussion around it rather than a summary of both.
They come with the issue. Images are uploaded to private storage, shown as thumbnails on the dashboard Issues page, and attached to the GitHub issue as a stable link that only workspace members can open.
File your next bug with one reaction. Issue tracking is on the free plan, and GitHub sync works as soon as you connect a repo.
Add Viably to Slack