Project Integrations

The Integrations tab enables connecting GitScrum with external services to synchronize development workflows and receive real-time notifications. Connect version control platforms to link commits and issues to tasks, or configure communication tools to receive project updates in your team's chat channels.

Overview

The interface displays a two-panel layout. The left sidebar lists all available integration providers organized by category. The right panel shows the configuration options for the selected provider. A counter in the header shows how many integrations are currently active.

Available Integrations

Native Integrations:

Slack - Webhook-based notifications to channels
Microsoft Teams - Webhook-based notifications to channels
Discord - Webhook-based notifications to channels
GitHub (Pro) - Repository connection with issue/commit sync
GitLab (Pro) - Repository connection with issue/commit sync
Bitbucket (Pro) - Repository connection with commit sync

External Integrations:

Zapier - Connect with 3,000+ apps
Pabbly - Workflow automations
API Docs - REST API documentation link

Communication Integrations

Slack, Discord, and Microsoft Teams use webhook URLs to receive notifications. The configuration process is identical for all three providers.

Connecting a Communication Platform

Select the provider from the left sidebar (Slack, Discord, or Teams)
Obtain a webhook URL from your platform:

Slack: Create an Incoming Webhook in your workspace settings
Discord: Create a webhook in channel settings
Teams: Add an Incoming Webhook connector to your channel

Paste the webhook URL in the Webhook URL field
Click Validate to test the connection
Optionally enter a Channel Name for reference
Toggle Integration Active to enable notifications
Click Activate Integration to save

Webhook Configuration Options

Webhook URL: The full webhook URL from your platform. Required field.

Channel Name: Optional label for your reference. Does not affect functionality.

Integration Active: Master toggle to enable or disable all notifications for this integration.

Notify Own Actions: When enabled, you receive notifications for actions you perform. When disabled, only actions by other team members trigger notifications.

Notification Events

After activating an integration, configure which events trigger notifications. Events are organized into expandable categories:

Task Lifecycle:

Task created
Task deleted

Task Status:

Task moved to different workflow stage
Task completed
Task blocked
Task unblocked

Task Assignment:

Task assigned to team member

Comments:

Comment created on task
User mentioned in comment

Sprint:

Sprint started
Sprint completed

Team:

Member joined project
Member left project

Each event has an individual toggle. Use the Enable All or Disable All links in category headers to quickly configure multiple events.

Testing and Managing

Test Connection: Click Test in the header to send a test notification to verify the webhook works correctly.

Remove Integration: Click Remove in the header to delete the integration configuration. A confirmation modal requires acknowledgment before deletion.

Version Control Integrations

GitHub, GitLab, and Bitbucket integrations connect repositories to synchronize issues, comments, and commits with GitScrum tasks. These integrations require a Pro subscription.

GitHub Configuration

Select GitHub from the sidebar
Generate a Personal Access Token at GitHub with repo and admin:repo_hook scopes
Paste the token in the Personal Access Token field
Click Save Token to validate and store
Click the refresh button to load your repositories
Select a repository from the dropdown
Click Connect Repository

GitHub Sync Settings

After connecting a repository, configure synchronization options:

Issues:

Create on issue opened: Creates a GitScrum task when a GitHub issue is opened. Optionally assign to a specific workflow stage.
Update on issue closed: Moves the linked task when the GitHub issue closes. Optionally move to a specific workflow stage.
Update on issue reopened: Updates task status when issue is reopened.
Update on issue edited: Syncs title/description changes.
Delete on issue deleted: Removes linked task when issue is deleted.

Comments:

Sync new comments: Adds GitHub issue comments to linked tasks.
Sync edited comments: Updates task comments when GitHub comments change.
Remove deleted comments: Deletes task comments when GitHub comments are removed.

Commits & Pull Requests:

Link commits to tasks: Associates commits mentioning task IDs with tasks. Use task codes in commit messages to auto-link.
Move on merge: Optionally move linked tasks to a specific workflow stage when commits are merged.

GitHub Additional Actions

Import Issues: Click Import Issues to import existing GitHub issues as GitScrum tasks.

Disconnect: Click Disconnect GitHub to remove the repository connection.

GitLab and Bitbucket

GitLab and Bitbucket follow the same configuration pattern:

Generate a Personal Access Token from your platform
Enter the token and validate
Select and connect a repository
Configure sync settings for issues, comments, and commits

External Integrations

The sidebar includes links to external integration platforms:

Zapier: Opens the GitScrum integration page on Zapier where you can connect with 3,000+ applications using automated workflows.

Pabbly: Opens the GitScrum integration page on Pabbly for creating workflow automations.

API Docs: Opens the GitScrum REST API documentation for building custom integrations.

These links open in new browser tabs and do not require configuration within GitScrum.

Integration Status Indicators

Each provider in the sidebar shows its current status:

Green dot + "Connected" - Integration is active and working
"Not configured" - No integration set up for this provider
Active counter - Header shows total number of active integrations

Best Practices

Start with essential events: Enable only critical notifications initially, then expand based on team feedback.
Use channel naming: Add descriptive channel names to easily identify which channel receives which notifications.
Test before deploying: Always use the Validate and Test buttons before relying on an integration.
Review regularly: Periodically review enabled events to prevent notification fatigue.

Webhooks - Custom webhook configuration for advanced automation
API Access - Generate API tokens for custom integrations