The practice I’m discussing is: Your project/product has a ticketing system for bugs, features, etc. There is also have source control. However, it always seems that there is a reason to try to tie these two together. Some places don’t want a checkin without a ticket number. Some development shops are looser about the requirement that there exist a ticket for every checkin, and will let in a minor checkin or two slide without a ticket number attached.
Question: What makes this practice so useful?
I’ve seen this practice in various places in my career. This is especially evident in products such as Microsoft’s Team Foundation Server. I’ve seen in at IBM with CMVC, their home grown source code management system. I’ve seen in with Mingle and SVN, or SVN and Redmine, where you can associate tickets to checkins by simply putting the ticket number in the commit message. In all these places, I really haven’t found it to be useful in my own work, so I realize that it should be useful somewhere down the line.
It tells you :