I think you're on to something. I do find it interesting that I've noticed many product managers use ticket systems to track and reference work and changes, wh

I think you're on to something. I do find it interesting that I've noticed many product managers use ticket systems to track and reference work and changes, while programmers use version control systems to do something very similar. These two systems often link to each other via hyperlinks in ticket systems and ticket numbers in commit messages. The most coupled systems like git and Github Issues are still at arm's length to one another. Even Fossil (to the best of my knowledge) considers tickets and source commits/branches/etc to be separate entities. Maybe there's something worth looking into there that integrates the concepts more than just links and hooks. The bigger issue IMHO is that rush of endorphins when I complete a ticket. It's more fulfilling to me when I can quantify my productivity, and tickets allow me to do that. But that combines with the idea that your work = your worth, which is completely untrue. That's the core issue that I'm still trying to work on for myself.