Part

Ticket source

You might say: intake, feedback button, monitor, error tracker

Something outside the tracker that supplies a request or observation. It can create a ticket directly or send evidence for a human or task to file.

What it does
Converts outside signals into durable work while preserving enough context to trace the signal back.
Ask
What creates this signal, and what prevents the same signal from filing the same ticket twice?
Typical
Feedback button, monitor, error tracker, scanner, inbox, or another webhook producer. Deduplicate by external event id or fingerprint grouping before opening another ticket.
Trouble
A noisy source floods the tracker, loses context, or creates duplicate tickets.

What to look for

  1. An incoming event, alert, or form entry
  2. A source URL or external event id on the ticket
  3. An intake rule that maps signals to a project or label

Catalogue: Source kind

Connections

Sources

  1. GitHub, About webhooks, About webhooksWebhooks let you subscribe to events happening in a software system and automatically receive a delivery of data to your server whenever those events occur.
  2. Sentry, Event fingerprinting, Event fingerprintingAll events have a fingerprint. Events with the same fingerprint are grouped together into an issue.

Use it on your project

teardown-apply: hold "Ticket source" (ticket-source) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal