Git Integration Disconnected from Project Management

When Git repositories and project management live in separate worlds, teams lose visibility into what code supports which tasks. GitScrum integrates with GitHub, GitLab, and Bitbucket to connect commits, branches, and pull requests directly to tasks.

The Disconnection Problem

Separate Git and project management creates friction:

• Manual updates — Marking tasks complete after merges
• Lost context — No visibility into which commits support which tasks
• Duplicate effort — Writing PR descriptions and task updates
• Audit gaps — Tracing features back to original requirements
• Reporting overhead — Manually correlating code and task progress

GitScrum Git Integrations

Connect your repositories to GitScrum:

Supported Platforms

What Gets Connected

• Commits linked to tasks via task ID in commit message
• Branches tracked per task
• Pull/Merge Requests visible in task timeline
• Status changes reflected automatically

Setting Up Git Integration

GitHub Setup

1. Go to Project Settings → Integrations
2. Select GitHub
3. Authenticate with OAuth
4. Select repositories to connect
5. Configure sync options

GitLab Setup

1. Go to Project Settings → Integrations
2. Select GitLab
3. Enter personal access token
4. Select projects to connect
5. Configure webhook notifications

Bitbucket Setup

1. Go to Project Settings → Integrations
2. Select Bitbucket
3. Authenticate with OAuth
4. Select repositories to connect
5. Configure sync options

Linking Commits to Tasks

Use task IDs in commit messages to link:

Commit Message Format

git commit -m "Add user authentication [GS-234]"

Alternative Formats

# Short form
git commit -m "Fix login bug #234"

# With description
git commit -m "Implement OAuth flow

Adds Google OAuth support for user authentication.
Closes GS-234"

# Multiple tasks
git commit -m "Refactor auth module [GS-234] [GS-235]"

What Appears in GitScrum

Task #234: Implement OAuth login
├── Status: In Progress
├── Git Activity:
│   ├── Commit abc123: "Add user authentication [GS-234]"
│   ├── Branch: feature/oauth-login
│   └── PR #45: "OAuth Implementation" (Open)
└── Last updated: 5 minutes ago

Branch Tracking

GitScrum tracks branches associated with tasks:

Branch Naming Convention

feature/GS-234-oauth-login
bugfix/GS-456-login-error
hotfix/GS-789-security-patch

Branch Visibility

• See active branches per task
• Track branch status (open, merged, deleted)
• View branch history in task timeline

Pull Request Integration

PR Visibility in Tasks

When PRs reference task IDs:

Task #234: Implement OAuth login
├── Pull Requests:
│   └── #45: "OAuth Implementation"
│       ├── Status: Open
│       ├── Author: @developer
│       ├── Reviewers: @senior-dev
│       ├── Checks: ✓ All passing
│       └── Comments: 3

Automatic Status Updates

Configure auto-transitions:

• PR opened → Task moves to "In Review"
• PR merged → Task moves to "Done"
• PR closed → Task returns to "In Progress"

Activity Timeline

Each task shows Git activity chronologically:

Task #234: Implement OAuth login
Timeline:
├── Dec 18, 10:00 — PR #45 merged by @senior-dev
├── Dec 18, 09:30 — PR #45 approved by @senior-dev
├── Dec 17, 16:00 — PR #45 opened by @developer
├── Dec 17, 15:45 — Commit def456: "Add OAuth callback handling"
├── Dec 17, 14:00 — Commit abc123: "Add OAuth initialization"
├── Dec 16, 10:00 — Branch feature/GS-234-oauth-login created
└── Dec 15, 09:00 — Task created by @pm

Bidirectional Linking

From GitScrum to Git

• View commits, branches, PRs in task details
• Click through to GitHub/GitLab/Bitbucket
• See PR status and review comments

From Git to GitScrum

• Add links to tasks in PR descriptions
• See task context when reviewing PRs
• Access task requirements from commit history

Best Practices

Commit Message Standards

1. Include task ID — Every commit references a task
2. Be descriptive — Explain what and why
3. Keep it atomic — One logical change per commit
4. Use conventional format — type(scope): message [task-id]

Branch Strategy

1. Use task ID in branch name — Automatic linking
2. Keep branches short-lived — Merge frequently
3. Delete after merge — Clean repository

PR Workflow

1. Reference task in PR title or description
2. Use PR template that prompts for task link
3. Review task requirements before approving

Automation Opportunities

Auto-Move Tasks on Git Events

Webhook Notifications

Send Git events to GitScrum:

• Commit pushes
• PR status changes
• Branch creation/deletion
• Review requests

Related Solutions

• GitHub project management integration
• GitLab workflow automation
• Developer workflow optimization