Configuring application wide integration settings for FogBugz in Test Collab:

While defining the application wide issue manager settings you need to provide the URL for the Fogbugz instance you want to associate, along with the email and password as part of the access credentials.

You also have an option of allowing the reported issue to be resolved automatically when the related test case passes by checking "Resolve reported issues when a failed test case is marked as passed". When you check this you will be prompted to provide the status code that Fogbugz uses for resolved issues, you need to enter the same for "Status code for resolved".

Project wise integration settings 

When it comes to project specific settings, values for following fields can be provided for Fogbugz, please note that all these fields are optional:

Project - Fill your project ID here. Use exactly same name as it is specified in your FogBugz.

Area - In Fogbugz each project is divided into functional areas. Use exactly same name as it is specified in your FogBugz like Code, Documentation, User Interface etc..

Category - Here you can specify that the issue you are reporting is a bug, feature or a question. Use exactly same name as it is specified in your FogBugz like Bug, Feature, etc..

Assigned to user id - Provide the name / id of the user to whom you want to assign all defects created from Test Collab. 

Priority - You can define the priority of the case here. You can provide the code for priority in value field

Tags - If you want your reported cases to have any tag then you can simply write your tags in the value field. You can provide more than one tags by separating them with a comma

You can also add other fields including any custom field using "Add user defined field" from the drop down, clicking this you will get a text box in place of drop down to enter the  name of the field.

A completed project specific issue manager setting form for Fogbugz would look like this.

Once the values for all fields have been provided you can save and test the settings by creating a sample issue in FogBugz.

Did this answer your question?