Engineering

From bug report to filed ticket

Reported to filed in under a minute, with better tickets.

The prompt

“Turn this Slack thread into a Linear ticket: extract repro steps, search our GitHub for related code and duplicate issues, file it with priority and links, then post the ticket back to the thread.”

  • GitHub
  • Linear
  • Slack
The flow
  1. Read the bug report thread
  2. Search the repo for the suspect code path
  3. Check for duplicate issues
  4. File a ticket with repro steps, logs, and links
  5. Reply in the thread with the ticket link

Side by side

The same job, by hand and through Spinrun

Doing it by hand

The grind

  • A bug lands in #support and dies there.
  • Filing a good ticket means chasing repro steps across three tools.

With Spinrun

  • Writes to connected apps wait for your approval by default, on every plan
  • Connected once through OAuth and kept in an encrypted vault.
  • Every call is in the activity log with the user, the tool, the action and the outcome.

Toolkits

The apps it touches

Run it with your apps.

Start on the free plan. No card required.

Before anything loads

We would like to switch on analytics, so we can see which pages are worth keeping. Nothing has loaded yet and nothing will until you choose. The cookies that keep you signed in and remember your language are not part of this.

Read the Cookie Policy