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 gets lost in the handoff.

Add to Slack See pricing

#product — Slack

Today

KM

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

Filing

However it gets mentioned, it gets tracked

React to a message, describe the bug to @Via, fill in a modal, or point Via at a noisy launch thread and let it file the real blockers. Every path lands the same tracked issue with a link back to the thread.

#product — Slack

Launch day

SH

Stanley9:02 AM

annual-plan switch is 500ing for me too 🔴

KM

Kevin9:03 AM

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

AM

Angela9:05 AM

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

JH

Jim9:06 AM

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

OM

Oscar9:07 AM

@Via read this whole thread and file anything blocking launch

ViaApp9:07 AM

✨Triaged 42 messages, filed 3 issues

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. It isn't blocking launch, so I didn't clutter the board with it.

Today

KM

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 and they attach to the issue automatically.

🐛 Create IssueDismiss

React 🐛, 🪲 or 🐞 on any message and Via drops a button card in the thread, filled in from the words already written. Nobody copies anything or leaves the channel.

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

The full lifecycle

Follow one bug from filed to fixed

Issue #218 opens a linked GitHub issue, breaks into sub-tasks, stays in front of the team in Slack and the Monday digest, and closes from wherever the fix lands. If the bug comes back, it re-opens with its history.

#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

#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█████░░░

Re-open

Open

In progress

Resolved

/issuesFrom the list

🔵 #218 Checkout 500s✅ Resolve

One tap closes it. If nobody is assigned, Via asks who fixed it first.

AI cardFrom the issue card

🐛 #218 Checkout 500s on annual-plan switch

✅ Mark Resolved

Records who closed it and when, and offers 🔄 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, so nobody needs to remember either.

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 shows up in

the issue card/issuesthe Weekly Pulsethe resolved card

Pick a repo on the confirm card and Via opens the GitHub issue through the Viably GitHub App, so nobody pastes a personal token. The link is stored once and shows up everywhere #218 does.

Command center

The whole board, live in the dashboard

Slack shows the top of the stack. The dashboard holds every issue with the same status and assignee filters, and nobody has to re-run a command to see it change.

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

From the blog

Read how we use it

Slack bug report: a template, a severity guide, and a shortcut

How to write a Slack bug report engineers can act on: a free template, a severity guide, and one reaction that turns any thread into a full report.

Slack issue tracking: 4 apps compared, and how to file bugs from a thread

Jira, Linear, GitHub, and Viably compared for Slack issue tracking, plus how to file a bug from any thread with one reaction and track it with GitHub sync.

Bug triage that never leaves Slack

Every bug reported in a support channel pays a tax before it becomes a tracked issue: copying error text, guessing severity, remembering to link back. Here's how a single 🐞 reaction turns a Slack thread straight into a GitHub issue, kept in sync both ways.

Mentioned in Slack.Tracked to done.

Nothing lost in the handoff.

FAQ

Questions, answered

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 an issue filed in Slack opens on GitHub, and the Slack card gets a View on GitHub button. It's a one-way handoff: closing the issue in one place doesn't update the other. 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.