An Orphan Issue Is Not Delivery
Filing a ticket creates the appearance of progress while nothing is actually owned, scheduled, or moving.
I filed an issue for a real fix and treated “filed” as “handled.” It sat unassigned, unowned, nobody working it — until someone asked “who’s working on this?” and exposed that the answer was no one. The issue existed. The work didn’t.
Filing a ticket feels like progress. There’s an artifact, it has a number, the problem is captured. But an unowned issue is a TODO with extra steps. It has the shape of delivery and none of the substance.
The rule I took from it: file and route in one motion. An issue isn’t filed until it has a named owner and a path to an ETA. Creating the ticket and securing the owner are a single act, never “file now, route later.” Until it has an owner, the loop is open and I own driving it there — that turn, not eventually.
And the tell: if someone has to ask who owns X? about something you produced, you left an orphan. The fix isn’t to answer the question. It’s to route on file, every time, so the question never comes up.