Source Control Integration

FogBugz can be set up to work together tightly with most source control systems. When you commit a bug fix to source control, you simply type the case number that you're fixing. The integration scripts see this and create bidirectional links:

1. From the FogBugz case to the source control history and diffs
2. From the source control system to the FogBugz case.

The benefits:

• You can implement a code-review process. Simply assign a case to the code reviewer. They click on the links to see the diffs in the source control system and review them.
• It's easy to find out how a bug was fixed by jumping straight to the source code change.
• When you're looking at the changes made in the source code and wondering why they were made, you can quickly jump to the bug they were intended to fix.

The exact mechanism for entering a case number when you commit changes depends on your source control system.

• Entering case numbers using CVS
• Entering case numbers using Subversion
• Entering case numbers using TortoiseSVN
• Entering case numbers using Perforce
• Entering case numbers using Visual SourceSafe
• Entering case numbers using SourceGear Vault

Before you can start using source control integration, you will need to make a few configuration changes to FogBugz and your source control system so they can talk to each other.

• Setting up CVS
• Setting up Subversion
• Setting up TortoiseSVN
• Setting up Perforce
• Setting up Visual SourceSafe
• Setting up SourceGear Vault
• Generic instructions for other source code control systems

If you don't already have source control, Fog Creek Software highly recommends Subversion. It's free, and available from http://subversion.tigris.org/. On all but the largest projects, it works just as well as more expensive source control systems and is extremely reliable.