Question

Can we get an overview of FogBugz's Source Control Integration feature?

Answer 1

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
• Entering case numbers using Mercurial
• Entering case numbers using Team Foundation Server

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
• Setting up Mercurial
• Setting up Team Foundation Server
• Generic instructions for other source code control systems

If you don't already have source control, we recommend Kiln.

Using Source Control Integration

When you have everything setup, source control integration in FogBugz allows you to associated changes you commit with a given case or cases. When you commit your changes in VCS, your hook script will look for something in your commit message that gives it a case number. For the scripts we distribute, the format is "BugzID: XYZ" where XYZ is a case number. The hook script then posts the info to FogBugz.

When you look at the case you referenced (number XYZ) in FogBugz, you will see a link on the left side of the case, "checkins".

When you click the link, a pop-up dialog appears, showing all of the files and revisions committed against the case.

Based on your configured URLs in Admin -> Source Control, the file paths and revision numbers will link to an external system to show you file and diff views.