Integration with FogBugz 4.0.15 and Source Vault 3.0.4

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
steve parsons

Integration with FogBugz 4.0.15 and Source Vault 3.0.4

Post by steve parsons » Fri Aug 26, 2005 1:49 am

I'm trying to get the integration of FogBugz to work with our installation of Source Vault.

I'm not having any joy at present, neither the source control app seems to see FogBugz, or vice versa.

In Source Vault admin I've configured the following options for all of our source code repositories:
Bug Tracking Application = FogBugz
Bug Tracking Integration URL = http://dev2000/FogBugz/

I've also set the following settings in the site page of FogBugz:
Source Control URL for logs = http://dev2000/VaultService/VaultWeb/Va ... File=^FILE
Source Control URL for diffs = http://dev2000/VaultService/VaultWeb/Va ... ersion=^R2

Source Vault doesn't seem to enable the Update Bugs window, so I can't enter a case number and I'm not seeing any source control references in the FogBugz case either.

Both our source control and bug tracking software run on the same system, so I've tried substituting in localhost, instead of dev2000 for the server name in both the Source Vault and FogBugz apps, but had no success with this either.

One issue I have is that the URLs for Source Vault require a login, but FogBugz doesn't appear to support a means of entering this information.

Any advice on the above would be much appreciated,
Steve Parsons.

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Fri Aug 26, 2005 8:32 am

It looks like you have things set up properly.
Source Vault doesn't seem to enable the Update Bugs window, so I can't enter a case number and I'm not seeing any source control references in the FogBugz case either.
Do you have any items in the checkin dialog that have a status of "modified" or "added"?

The update bugs section is only enabled if there is at least one item in the checkin that is selected for checkin that is modified (or added).
One issue I have is that the URLs for Source Vault require a login, but FogBugz doesn't appear to support a means of entering this information.
The only integration mechanism that FogBugz provides for SCC providers is the logs and diff URLs. FogBugz doesn't have any "Vault specific" features. You will need to manually log into Vault web from Fogbugz.
Mary Jo Skrobul
SourceGear

steve parsons

Post by steve parsons » Tue Aug 30, 2005 7:17 am

Seems to all be working now - thanks for your help.

Post Reply