How do I file an issue from Slack?

React to any message with the 🐞 bug reaction. Via reads the thread, extracts a title, summary, and severity with AI, and creates a tracked issue, with no form to fill in.

Does it sync to GitHub?

Yes. Connect a repo and issues sync two ways: filed in Slack they open on GitHub, and updates on GitHub reflect back on the Slack card. You choose which repos allow issue creation.

Can I attach screenshots?

Images in the Slack thread are captured with the issue, so whoever triages it sees the evidence alongside the AI-written summary.

How is severity decided?

Via infers severity from the message content when it files the issue, and you can adjust it any time on the card or in the command center.

Where do I manage all issues?

The web command center holds every issue on a kanban board, with status columns, assignees, and GitHub links in one place.

Issue tracking

Bugs caught the moment they're mentioned.

React 🐛 on any message, describe it to @Via, or file it straight from a modal. Every path lands the same tracked issue — with a link back to the thread, so no detail is lost in the handoff.

Add to Slack See pricing

#product — Slack

Today

Kevin10:42 AM

Checkout is throwing a 500 on the annual plan switch 😬

ViaApp10:42 AMGitHub

🐛Issue #218 created

Repo: viably/on_next
Assignee: @oscar
Priority: High
Status: Open

Three doors

However it gets mentioned, it gets tracked

There's no one way to report a bug — so Viably meets the moment three ways. Take the tour, or click straight to the one your team would reach for.

#product — Slack

Today

Kevin10:42 AM

Checkout is throwing a 500 on the annual-plan switch 😬 anyone else seeing this?

ViaApp10:42 AM

🐛Bug flagged in Slack

Checkout is throwing a 500 on the annual-plan switch

📎 Got screenshots? Paste them as replies in this thread — they attach to the issue automatically.

🐛 Create IssueDismiss

The passive trigger. React 🐛, 🪲, or 🐞 on any message and Via drops a button card in the thread — pre-filled from the words already written. Zero copy-paste, zero context switch.

··

Issue #218 is tracked, with a link back to the thread

Thread triage

Point @Via at the chaos. Get scoped issues back.

A launch thread is a pile-up of half-reported bugs. Ask Via to read the whole thing and it files the real blockers — scoped, assigned, GitHub-linked — and leaves the noise alone. Not transcription. Triage.

#launch — Slack

Launch day

Stanley9:02 AM

annual-plan switch is 500ing for me too 🔴

Kevin9:03 AM

and the checkout button straight up vanishes on iOS Safari when the cart's empty

Angela9:05 AM

webhook retries are hammering us — 200+ in the logs this hour 😵

Jim9:06 AM

related to the 500s? also the receipt OCR dropped a couple line items earlier, minor though

Oscar9:07 AM

@Via read this whole thread and file anything blocking launch

ViaApp9:07 AM

✨Triaged 42 messages → 3 issues filed

Three launch blockers, scoped and assigned. The checkout regression is linked to GitHub.

#218 Checkout 500s on annual-plan switch

@oscar

GitHub

#219 Checkout button vanishes on iOS Safari (empty cart)

Unassigned

#220 Webhook retry storm — 200+ retries/hr

@angela

Left the OCR line-item nit out — not blocking launch, so I didn't clutter the board with it.

The full lifecycle

Open to resolved — and back, if it returns

Every issue rides the same pipeline. Break a gnarly one into linked sub-tasks, close it from any of three places, and re-open it with the history intact if the bug comes back.

Re-open

Open

In progress

Resolved

Big bug? Link tasks to it as sub-tasks and watch the work close in:

ViaApp2:31 PM

🐛 #218 Checkout 500s on annual-plan switch

Linked sub-tasks2 of 4 done

Reproduce on staging@angela

Patch the billing serializer@oscar

Add a regression test@oscar

Deploy + verify in produp for grabs

Resolve when you're satisfied it's fixed.✅ Resolve

And close the loop from wherever you already are:

/issuesFrom the list

🔵 #218 Checkout 500s✅ Resolve

One tap closes it. Unassigned? Via asks who fixed it first.

AI cardFrom the issue card

🐛 #218 Checkout 500s

✅ Mark Resolved

Records who closed it and when — with a 🔄 Re-open if it comes back.

@ViaFrom a sentence

@Via the checkout bug is fixed

Resolved #218 — nice work

Via matches the issue by title or ID. No buttons, no IDs to memorise.

Stays visible

Open issues don't get forgotten

Filter the whole board in a sentence — keywords mix freely. Then let the digests do the chasing: open issues surface every Monday, and resolutions get counted and celebrated every month.

/issues — Slack

/issuesopen

Issues

Open issues · all assignees

#219 Checkout button vanishes on iOS Safari (empty cart)unassigned

#220 Webhook retry storm — 200+/hr@angela6d

Showing 2 · keywords are order-independent — mix status, assignee, and due.

#team — Slack

ViaAppMon 9:00 AM

🗓️ Your Weekly Pulse

Where the team stands — Monday 30 June

🐛 Open issues — 2

🔴 #218 Annual-plan checkout 500 — @oscar

🔴 #219 Checkout button vanishes on iOS — unassigned

Every Monday, open issues surface in the Weekly Digest — owners named, nothing quietly forgotten.

#team — Slack

ViaAppTue 1 Jul, 9:00 AM

📊 June 2026 — Month in Review

What the team shipped last month 🎉

🐛 Issues resolved0

🏆 Medal champions of the month

🥇@jim+34████████

🥈@oscar+27██████░░

🥉@angela+21█████░░░

Resolutions get counted — and when teammates 🏅 a sharp bug-squash, that recognition lands the resolver on the champions podium.

GitHub

One click opens a linked GitHub issue

Pick a repo on the confirm card and Via opens the issue through the Viably GitHub App — no personal login, no token to paste. The link is stored once and shows up everywhere the issue does.

Slack

🐛 #218 Checkout 500s on annual-plan switch

Also open on GitHub?viably/on_next

GitHub

Checkout 500s on annual-plan switch #342

Openopened by viably-app[bot]

The link is stored once — then it rides along in

the issue card/issuesthe Weekly Digestthe resolved card

Command center

The full board lives in the dashboard

Slack shows the top of the stack; the dashboard holds every issue, with the same status and assignee filters — live, no command to re-run. Try them:

Issues — command center

Issues

#218 Checkout 500s on the annual-plan switch

Reported by @Kevin·@oscar

viably/on_nextIn progress✅ Resolve

#219 Checkout button vanishes on iOS Safari (empty cart)

Reported by @jim·unassigned

Open✅ Resolve

#220 Webhook retry storm — 200+/hr

Reported by @angela·@angela

viably/on_slackOpen✅ Resolve

#214 Reminder DST off-by-one near the cutover

Reported by @stanley·@stanley

viably/on_slackIn progress✅ Resolve

Showing 4 of 6View & archive

Mentioned in Slack.Tracked to done.

Nothing lost in the handoff.

FAQ

Questions, answered

Read the full guideIssue Tracking from Slack

Ready when you are

Assemble your operating system inside Slack.

Add Viably free. Turn on the powers your team needs, when you need them.

Add to Slack See pricing

SignalRecordOwned work

Free to start
The free plan needs no card
Powers on when you need them