The author gets so close to the productive answer regarding TODOs, it's frustrating to see the conclusion be "...so never add TODO comments at all." So what, a

The author gets so close to the productive answer regarding TODOs, it's frustrating to see the conclusion be "...so never add TODO comments at all." So what, after creating the issue for the future, the person implementing it has to start over navigating the code? And the next person working on the code (who might not know about that issue) might stumble across the same obstacles as the original author who went on to file the issue? I think in any multi-programmer project, the bidirectional link code<->issue needs to exist.