ViablyViably
Sign in
🐛Issues Power

Capture every bug, without leaving Slack

Most bugs first surface as a passing complaint in a channel and then drift away. Viably promotes any Slack message into a tracked issue with a single reaction — and uses AI to give it a real title, summary, and severity automatically.

How it works

  1. 1

    Someone reports a bug in chat

    A teammate or customer-support relay posts a message describing what went wrong. No special command needed — Viably just sees it as a normal Slack message.

  2. 2

    React with a bug emoji

    Add 🐞, 🪲, or 🐛as a reaction. Viably treats any of these as the "file this" signal.

  3. 3

    Viably turns it into a structured issue

    With AI Chat enabled, Viably reads the thread and infers a title, longer description, and severity. Without AI, the raw text becomes the issue body — nothing is lost.

  4. 4

    Posted 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.

Triggers

Three independent ways to file an issue. They all converge on the same workflow.
TriggerUse when
🐞 / 🪲 / 🐛 reactionPromoting an existing message — the fastest path.
/issues createFiling a fresh issue when there is no triggering message.
Ask Via directlyIn AI Chat: "create an issue: signup form doesn't accept + in email".

AI extraction

When AI Chat is configured (any provider key on the AI Chat config page), Viably uses the LLM to enrich each issue with:
  • Title — a concise summary, ready for an issue tracker.
  • Description — reproduction steps, expected vs actual, and links from the thread.
  • Severity — low, medium, high, or critical, based on impact cues in the text.
No AI key? Viably falls back to using the raw thread text as the issue body. The reaction-driven workflow still works — you just don't get the auto-extracted title or severity.

GitHub sync

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 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 (network blip, repo just deleted), Viably keeps the Slack-side issue and surfaces the error in the thread — never silently lost.

Screenshots & images

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 only accessible to authenticated workspace members.