Open Category List

Working With BTS (Bug Tracking System) Connectors

6 minutesread

This article provides general information about working with the BTS Connectors, as part of setting up the integration between the Applause platform and your Bug Tracking System. Learn more about integrating with your BTS here

For additional information about a specific BTS, see the links below:

BTS Specific Integration Information

BTS Issue Settings

Once you have enabled the BTS Integration for the product, selected the relevant BTS and established connection with your BTS, the issue settings within your BTS will be returned to the Applause Platform. This allows you to configure what fields you would like to (or must to) send to your BTS to appear in the created issue. 

It’s important to note that when the integration is initially set, you are asked to establish the connection by clicking Test Connection. But, if the issue settings on your BTS have changed, you would need to refresh the connection, and – depending on the change – to edit the field mapping. Click the Refresh Connection button to do so. This will re-establish the connection, and provide the Applause Platform the latest issue settings from your BTS.

Note: To edit an existing connector, click the pencil icon next to the Connector Details header.

Fields, Values, and Mappings

Defining the BTS Connector is essentially a field-mapping task. This will allow you to map the Applause Platform fields to your BTS Issue fields, so that the Applause value will be used when the issue is created in your BTS. In some cases you may even need to map between specific values, thus allowing a dynamic creation of values in your BTS. And, in some cases, a complete customization of field value is allowed.

Mandatory vs. Optional Fields

As part of the Issue Settings acquired from your BTS, a breakdown of mandatory and optional issue fields will be available for the Applause Platform. The mandatory fields will populate the page and cannot be removed. Optional fields can be added and removed as needed.

Adding Optional Fields

To add an optional field:

1. While in the Integration step of the Edit Product wizard, click on the Add Field button, and select the field from the list of available fields. 

Note that if your BTS Issue settings include fields that are not available in the list you may need to refresh the connection, then try again.

2. The field will be added to the Field Configuration section. You may now continue to select its value – static, dynamic or custom.. 

Note that fields are added in an alphabetical order, which may differ from the way fields are presented in your BTS.

Removing Optional Fields

To remove an optional field, click the trash bin icon to the right of the field. Fields that do not have this icon are mandatory and cannot be removed.

Selecting Values

Once the field is selected, you will need to set the value that will be sent to your BTS.

Static Values

To send a static value for a particular field, click on the dropdown list next to the field name. and select the static value. The selected value will be sent for all issues sent from the Applause Platform to your BTS.

A common example for static value will be a “Created By”. Many times users like to have issues created by the integration to be identified as such. In that case, you may want to map the integration user for this field as a static value.

Note: static value mapping is only allowed for fields with a predefined list of values.

To map a static value:

1. While setting a field (either mandatory or optional), click on the dropdown list next to the field name.

2. Select the BTS value.

Dynamic Values

Some fields support mapping of dynamic values. In these cases, the BTS field is mapped to an Applause field, and the field value is pulled from the Applause Platform. As the intent of the integration is to create the new issues in your BTS with their relevant, accurate information, most probably most of your field mappings will be of dynamic fields.

Common examples for dynamic fields will be “Action taken”, “Expected Result” and “Actual Result”. You would clearly want these fields to have the values provided by the tester for each specific issue. In that case, you will probably want to map those fields to their corresponding fields in Applause.

To map a dynamic value:

1. While setting a field (either mandatory or optional), click on the dropdown list next to the field name, and select the Applause field.

2. The dynamic value will be displayed as “${field name}”.

3. To clear the selection, either select another field or click on Clear

Unique Field Values: Issue Subject & Description

Two specific fields allow for unique customization – the issue subject (or title) and it’s description. 

In both cases, the customization allows for both static values, entered as free text, as well as dynamic values of multiple Applause fields. This enables you to display several Applause field values in a single BTS field.

Common examples will be:

  • Construct the issue subject from the Applause Bug Subject, Bug Id, Severity and Type. For instance, “Bug #1234: Nothing works (Critical – Functional)”
  • Construct the issue description to include all reproduction steps, including steps taken, expected results and actual results. 

To map a unique field value:

1. While setting the Issue Subject or Description fields, click on the dropdown list next to the field name, and select [Custom…].

2. The unique value text box will be displayed. You may type in whatever free text as static value.

3. To add a dynamic value, use the dropdown list to the right of the unique value text box, and select the Applause field. 

4. The dynamic value will be displayed as “${field name}”. You may do this multiple times and add several Applause fields.

In addition to the unique customization allowed for the Issue Description field, there are three default template options – Full, Compact, Bare Minimum – you may choose from.

Custom Mappings 

In addition to static and dynamic value mapping, at times you may need a more advanced mapping. Custom mappings allow you to map specific field values in Applause Platform to the matching field values in your BTS. This allows you to “translate” the Applause value assignment to your BTS’ “language”.

A common example for custom mapping will be for assigning the values of the “Priority” field in your BTS from values of the Applause field “Severity”. 

To custom-map values:

1. While setting a field (either mandatory or optional), click on the dropdown list next to the field name, and select [Custom…].

2. The option to select an Applause field will be displayed. Select one of the available fields: Severity, Bug Type, Approval Value Tier, Frequency or any uploaded test cycle custom field (see below).

3. The values of the selected Applause field will be displayed. Next to each of the fields, select a matching value of the BTS field you are setting. Note that you are able to map the same BTS field value to multiple Applause values.

 

Once all fields are selected and values are mapped, remember to save the product settings.

Uploading Test Cycle Custom Fields

As you set the Custom Mapping you may want to use values set for issues by the testers for custom fields set on test cycles. Learn more about adding custom fields while creating or editing test cycles here. Using the custom fields in your mapping allows you virtually unlimited options for collecting issue-level data from the testers, and have it included in the issues when those are created in your BTS.

In order to populate the list of fields available for custom mapping, you’ll need to upload them from the test cycle. Follow these steps:

1. While setting the BTS Connector, click to expand the Load Test Cycle Custom Fields option.

2. Input the test cycle ID, and click Load.

3. If the fields were uploaded successfully, a message will be displayed, and the fields are available for selection in the list of fields available for custom mapping.

0
1
1139
6 minutesread

Related Knowledge Base Posts