Clubhouse integration

Authentication

Supported authentication methods

Personal token

To proceed with this authentication type you need to obtain API token from Clubhouse. Steps below will instruct you how to do that.

Navigate to your Clubhouse and click on gear icon in the header to reveal the menu. Then click "Settings".

Reveal user menu

In "Settings" popup, go to "API Tokens" section. Provide desired name for your new token in "Token Name" field and click "Generate Token" to create new token.

Generate token

Note that when you generate a new token, the value will only be displayed once, so make sure to write it down.

Once you have the token, use it in Bugsee authentication wizard:

Enter token

Configuration

There are no any specific configuration steps for Clubhouse. 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 Clubhouse. For basic introduction, refer to custom recipe documentation.

Setting labels field

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

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

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

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

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

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