TargetProcess integration

Authentication

Supported authentication methods

Basic authentication

No custom configuration required in TargetProcess for this type of authentication.

Select "Basic authentication" in the first step of integration wizard. Click "Next".

Select basic authentication

Provide valid host (URL to your TargetProcess), username and password. Click "Next".

Provide URL

Personal token

No custom configuration required in TargetProcess for this type of authentication.

Start Bugsee integration wizard and select "Personal token" authentication type. Click "Next".

Select personal token

Provide valid host (URL to your TargetProcess, usually in form of https://<domain>.tpondemand.com).

Provide URL

You will be presented with a dialog with a token. Copy it and close the dialog.

Copy token

Paste token copied in previous step. Click "Next".

Paste token

Configuration

There are no any specific configuration steps for TargetProcess. Refer to configuration section for description about generic steps.

Custom recipes

Bugsee can accommodate all these customizations with the help of custom recipes. This section provides a few examples of using custom recipes specifically with TargetProcess. For basic introduction, refer to custom recipe documentation.

Setting tags field

By default Bugsee creates and updates TargetProcess bugs with Bugsee issue labels as TargetProcess tags. But labels list can be overridden inside your custom recipe. For example you can add some new label (TargetProcess tag) to existing ones:

function create(context) {
    // ....

    return {
        // ...
        labels: [...issue.labels, "My awesome tag"]
    };
}

function update(context, changes) {
    const result = {};
    // ...

    if (changes.labels) {
        result.labels = [...changes.labels.to, "My awesome tag"];
    }

    return {
        issue: {
            custom: {}
        },
        changes: result
    };
}