February 5th, 2015 by Derrick Miller
FogBugz is great at keeping a full audit history of changes in a case. It ensures the information you need doesn’t get lost. Kiln is great at keeping your source code centrally located. It’s also great at allowing you access to the full audit history of your code. These are two distinct audit histories. However, often a case is a bug or a feature request which means that code is written and pushed to Kiln to solve it. So our FogBugz and Kiln integration helps you to see both of these histories in one place: the FogBugz case.
Below, we’ll talk about the benefits of this integration, how you can quickly integrate the two products yourself, and a few tasty bonus tips to finish off.
What’s so great about FogBugz and Kiln integration?
It all starts with a case. A case has full audit history; any change, any comment, anything. Kiln has a full audit history as well; who committed, who pushed, who authored – and when. Since a case represents a feature, a bug, or any other category of work that affects code – why not merge these histories upon a FogBugz case to see how your code changes over time in relation to the case?
That’s what Kiln set out to do. It gives you a natural history of events on your FogBugz case of your changeset history in Kiln. Voilà – a full-circle single-view audit history.
While viewing a FogBugz case that has associated changesets in Kiln, you will see several important pieces of information:
1. The changeset between your case edits and/or emails
2. List of code reviews that include changesets associated to the case
3. Number of changesets associated to this case
4. Ability to create a code review
5. List of changesets associated to the case
6. The short changeset ID
7. The author of the changeset
8. The time the changeset was committed
9. The repository the changeset is in, and if the changeset shows up in any related repositories
10. List of tags on this changeset
11. The changeset’s commit message
Complete the Integration
All you need to complete the integration is a FogBugz case number. Include your case number in the changeset’s commit message and Kiln will automatically link the history with the case.
git commit -m "fixing bug 495 - making todo item show strikethrough formatting when checked off"
Or, associate a case to a changeset after you have pushed to Kiln.
We took this a step further and added Kiln Code Reviews to the case as well. This way you can see not only the full case history and associated changeset commit history, but the associated Code Reviews to the changesets on the case. It’s all there, in one historical view.
A Few More Tricks
- If a case has changesets associated with it, then you can create a code review on those changesets directly from the FogBugz Case. Click “Request Review”, then click the “Review” button on any of the changesets. One stop shopping.
- If you mention the review number in your case comments, then FogBugz will automatically link to your Code Review.
- Similarly, if you put the short changeset ID in your case comment, then FogBugz will automatically link a Kiln search for that changeset ID.
- In Kiln, while viewing a changeset, not only can you add a case to the changeset, but you can also see a list of the cases already associated to the changeset, or remove the association.
- FogBugz, when displaying the changesets on the case, will respect your Kiln permissions. If someone can view a case, but doesn’t have access to the repository in Kiln, then they will not see the Kiln changeset and commit message.
When a changeset from Kiln is associated with a FogBugz case, you get the full circle history of your bugs or features. The easiest way to get started is to click “Add a case” on any changeset in Kiln today and input a case number!