Issue tracker

The system of record where engineering work is queued, assigned, and closed — GitHub Issues, Jira, Linear.

An issue tracker is where work becomes real. A problem described in chat is a conversation; the same problem in the tracker is a commitment with an owner and a state.

This is why routing matters more than collecting. Feedback that sits in a separate tool is feedback that has to be triaged twice — once to decide it is real, and again to re-enter it where the work happens.

Filing directly into the tracker has a cost: noise. The mitigation is not to add a manual step, but to make the intake form structured enough that a triager can dismiss or promote a report in seconds.

Why it matters

Work that is not in the tracker does not get scheduled. Feedback that never reaches the tracker never gets fixed.