FogBugz service management

With this service, you can integrate Bitbucket with FogBugz, an issue-tracking and project-management system. If you are having trouble with the service, see Troubleshoot Bitbucket services.

Setting Up the service

 You must have administrative access on a repository to add this service.

  1. Go to the repository's settings.
  2. Click Services in the left-hand navigation.
    The Services page appears.
  3. Select the FogBugz service from the services dropdown.
  4. Click Add service.
    A new section appears for the FogBugz service.
  5. Enter the following information:

    Repository ID Enter the ID of the FogBugz repository.
    CVSSubmit URL
    Enter the URL to which Bitbucket should send its update messages. Do not specify any URL parameters, for example:https://your_repo.fogbugz.com/cvsSubmit.asp 
  6. Press Save.

Using the FogBugz in Your Commit Comment

When you create a commit message, put a mention of the BugzID string in the message like this:

git commit -m "This is a superb commit which solves case BugzID: 42"

Was this helpful?

Thanks for your feedback!

7 Archived comments

  1. User avatar

    Anonymous

    This doesn't work. Any more specific information?

    04 Oct 2011
  2. User avatar

    Anonymous

    This integration works well with BitBucket git repository. 

    In BitBucket service setup you need to specify only the url part WITHOUT any parameters, like this:

    Repository ID : 45

    CVSSubmit URL : https://your_repo.fogbugz.com/cvsSubmit.asp

    Then you will need to mention your FogBugz case ID in the commit message by putting "BugzID: ID" string in it (this is not documented anywhere :-( ) similar to this:

    git commit -m "This is a superb commit which solves case BugzID: 42"

    25 Nov 2012
    1. User avatar

      manthony

      Thanks for the input.  I've added it to the docs.  Unfortunately, I have yet to test each of these services pages. That's on my todo-list.  I didn't realize Fogbugz did not document their integration, usually I wouldn't document how to use another company's integration in case their implementation changed.  Since their integration isn't documented (as you point out), I've added that here also.

      This comment (and yours) will be removed within the week.

      26 Nov 2012
  3. User avatar

    Anonymous

    Is there a way to make it recognize #XXX as the case id instead of using that weird BugzId format?

    30 May 2013
    1. User avatar

      manthony

      You should make this suggestion to the FogBugz team.

      30 May 2013
      1. User avatar

        Anonymous

        Reading to the FogBugz documentation at this page it looks like the hook on Bitbucket is what parses the commit message looking for "BugzID". What gets sent to the FogBugz URL is a string with fields for the bug ID, file name, old and new revision IDs, and the repository ID that you enter in setting up the hook, nothing to do with the commit message itself.

        As far as I can tell it would be up to the developer who is responsible for the hook to change it so that it parses some more natural looking string such as "Case #" or perhaps even just "#". Whatever syntax you decide on does need to be documented here as it would not be part of the FogBugz side of things.

        08 Feb 2014
  4. User avatar

    Anonymous

    This does't seem to work for me, it leaves no comment in my fogbugz tickets.

    26 Sep 2013
Powered by Confluence and Scroll Viewport