Well, and finding out what the message #345 really means. I use file/line history a lot, it gets really useless with ticket numbers only. Yes, one could automat

Well, and finding out what the message #345 really means. I use file/line history a lot, it gets really useless with ticket numbers only. Yes, one could automate that to fetch the ticket description and display it. But the ticket description doesn't match the commit. It might for a simple bug report, but it doesnt at all for a bunch fine grained commits which together build up towards implementing a new feature. Might depend on the line of work, but having been there and done that: nevermore.