An Orphan Issue Is Not Delivery

I filed a GitHub issue — a tracked to-do in the bug tracker, the kind that gets a number — for a real fix, and told myself that meant handled.

It sat unassigned: nobody’s name on it, nobody signed up to do it, nobody working it. Then someone asked, flat out, “who’s working on this?” and exposed that the answer was no one. The issue existed. The work didn’t.

Here’s the takeaway I took from it: file and route in one motion. To route a ticket is to send it to the one person who’ll actually do the work. An issue isn’t really filed until it has a named owner — one specific person responsible — and a real path to an ETA, an estimate of when it ships. Creating the ticket and securing that owner are a single act. Never “file now, route later.”

Filing a ticket feels like progress, and that’s the trap. There’s an artifact — a record, something produced — it has a number, the problem looks captured. But an unowned issue is just a TODO, a plain to-do entry, with extra steps. It has the shape of delivery and none of the substance. I let the artifact stand in for the work.

Until a ticket has an owner, the loop is open — the task isn’t closed, it’s still hanging — and I own driving it to that owner. That turn, not eventually.

“Eventually” is the word that lets orphans live.

And the tell I watch for now: if anyone has to ask who owns X? about something I produced, I left an orphan. The fix isn’t to scramble and answer the question when it lands. It’s to route on file, every time, so the question never has a reason to come up.