Skip to documentation
ScrumPulseDocumentation
v2.0 docsSign in
Getting started

Connect your board

Configure and test a Taiga or Jira connection without exposing the board credential.

Last updated August 8, 2026

You can connect a board in the setup wizard or later under Settings → Integration.

Required permission: integrations:manage. Administrators have it automatically; an administrator can delegate it to another organization member.

Supported setup choices#

The current dashboard exposes two board types:

  • Taiga
  • Jira

The database model contains additional provider labels, but the customer-facing form and connection test only implement Taiga and Jira. Do not configure another value directly in the database.

Taiga connection#

  1. Open Settings → Integration.
  2. Set Board Type to Taiga.
  3. Enter the API base URL, such as https://api.taiga.io/api/v1.
  4. Enter the project slug or numeric project ID in Project Key / Slug / ID.
  5. Enter a Taiga API token in API Token.
  6. Select Test Connection.

ScrumPulse looks up the project by ID when the value is numeric and by slug otherwise.

Jira connection#

  1. Open Settings → Integration.
  2. Set Board Type to Jira.
  3. Enter the Jira site base URL.
  4. Enter the Jira project key.
  5. Enter an API token accepted by the Jira site.
  6. Select Test Connection.

ScrumPulse tests the Jira v3 project endpoint using the supplied key.

Save securely#

After a successful test, select Save Settings. The API encrypts the token before storing it. Later reads return a configured indicator instead of the raw token.

Entering a new token replaces the stored credential. Keep the previous token active until the replacement passes Test Connection, then rotate or revoke the old token in the provider.

Expected result#

The connection test returns the project name and reference. A successful settings save makes the integration available to dashboard-triggered runs for the current organization.

This does not configure the separate GitHub Actions scheduler. See Architecture and repository map.