Your Git workflow. Inside your tasks.
Connect GitHub, GitLab, or Bitbucket. Create branches from tasks with one click. Pull requests auto-link via task codes. Workflow updates on merge. No copy-paste. No context switching.
Branch creation to PR merge—tracked automatically in every task.
Your Git platform.
Already supported.
GitHub, GitLab, Bitbucket—connect any of them. Same workflow, same automation. Switch providers without losing functionality.
GitHub
Personal Access Token with repo and admin:repo_hook scopes. Webhooks for issues, comments, push, and pull requests
GitLab
Personal Access Token with api, read_repository, write_repository scopes. Webhooks for issues, notes, push, and merge requests
Bitbucket
Username + App Password authentication. Unified webhook endpoint for all repository events
Git meets tasks.
Zero friction.
One-Click Branches
Create branches directly from tasks. Auto-generated names: feature/--. No terminal, no copy-paste
PR Auto-Linking
PRs mentioning #TK-123 in title or description auto-link to tasks. No manual association required
Workflow on Merge
PR merged? Task workflow updates automatically. Configure target status per project. Close done, move to review
Issue Synchronization
Sync GitHub/GitLab issues to GitScrum tasks. Create, close, reopen—bidirectional when enabled
Commit Tracking
Commits with #TK-123 update task status. See commit history inside task drawer. Full traceability
Multi-Provider
Connect GitHub AND GitLab simultaneously. Switch between providers per task. One project, multiple repos
Task to branch.
In one click.
Open task drawer. Click create branch. Name auto-generated. Link in task. Start coding. No terminal commands.
Auto-Generated Names
feature/--<task-slug>
feature/API-847-fix-auth-timeout
Open task drawer
API-847 · Fix auth timeout
Click create branch
Branch created, linked to task
Open
PR awaiting review or changes
Merged
PR merged, task workflow updated
Closed
PR closed without merging
PRs linked.
Automatically.
Mention task code in PR title or description. GitScrum links it. See PR status, reviewers, merge state—all inside the task.
PR Information Tracked
- PR number and title
- Head → Base branch
- Author and avatar
- Merge timestamp
- Direct link to provider
Updates arrive.
Instantly.
Push a commit. Merge a PR. Close an issue. GitScrum knows immediately. No polling, no refresh needed.
GitHub Events
- issues
- issue_comment
- push
- pull_request
GitLab Events
- issues
- note
- push
- merge_request
Bitbucket Events
- repo:push
- pullrequest:*
- issue:*
- repo:refs_changed
Control what syncs.
Per project.
Enable issue sync, comment sync, commit tracking. Map workflows: issue closed → task done. Full control, no surprises.
Issues
- Create → Task created
- Closed → Workflow updated
- Reopened → Workflow updated
- Edit → Description synced
- Delete → Task archived
Comments
- Create → Comment added
- Edit → Comment updated
- Delete → Comment removed
Commits
- Push → Task workflow updated
- Message → Linked to task
Stay informed.
Your way.
Configure what Git events trigger notifications. Branches, commits, PRs, releases, CI/CD—enable what matters, disable the noise.
Branches
- Branch created
- Branch deleted
Commits
- Commit pushed
- Commit comment
Pull Requests
- PR opened
- PR closed
- PR merged
- Review requested
- Review submitted
- PR comment
Issues
- Issue opened
- Issue closed
- Issue comment
Releases
- Release created
- Tag created
CI/CD
- Workflow run
- Deployment
Full Git visibility.
Across all projects.
Your developers push code daily. You need to know what's shipping without joining standups or reading commit logs. Git integration gives you visibility into development progress through task updates—not through technical noise.
Progress Through PRs
When PRs merge, tasks move to done. You see delivery velocity without reading code
Branch-to-Task Mapping
Every branch tied to a task. Know exactly what code addresses what requirement
Multi-Repo Projects
Frontend repo on GitHub, backend on GitLab. Same project, unified task tracking
I don't read commit messages. I don't need to. When a PR merges, the task moves to done. I see what shipped today by looking at the board, not by opening GitHub.
Michael Torres
Founder, Digital Agency (38 developers)
Standups got 50% shorter. I can see which tasks have active PRs before the meeting. 'What's blocking you?' became 'Your PR has merge conflicts' because I already know.
Jennifer Walsh
Engineering Manager, SaaS Company
Development progress.
In real time.
You manage sprints. Developers work in Git. The gap between 'code done' and 'task updated' kills your planning accuracy. When PRs merge and tasks auto-update, your sprint board reflects reality—not yesterday's status.
Accurate Sprint Tracking
Task moves to done when PR merges. Sprint burndown updates automatically. No manual status updates
Branch Status Visibility
See which tasks have branches, which have open PRs. Know what's in progress without asking
Commit-to-Task Traceability
Every commit linked to its task. Audit trails built automatically. No documentation overhead
Stay in flow.
Git and tasks unified.
You're in terminal, pushing commits, opening PRs. Then someone asks you to update the task. Context switch. Open browser. Find task. Update status. Flow destroyed. What if tasks updated themselves from your Git activity?
Branch From Task Drawer
Click create branch. Name auto-generated: feature/API-847-your-task. Copy to clipboard. git checkout. Done
Commit Messages Work
git commit -m 'Fix timeout #TK-847'. Task workflow updates. No separate action needed
PR Mentions Auto-Link
Open PR with 'Fixes TK-847' in description. PR appears in task drawer. Merge → task done
I haven't manually updated a task status in months. Create branch from task, commit with task code, merge PR. GitScrum figures out the rest. I just write code.
Alex Chen
Senior Backend Developer
My agency used to say things were 'almost done' for weeks. Now I watch the board. When tasks move to done, code shipped. It's transparent without me needing to understand the code.
Robert Kim
Product Owner, E-commerce Platform
See real progress.
Not estimates.
You're told 'it's 80% done' but have no way to verify. With Git-linked tasks, you see when code actually ships. Task moved to done? Code merged. Not 'developer says done'—actually deployed.
Verified Completion
Task status changes when code merges. You see objective progress, not subjective estimates
Sprint Reality
Board reflects what's actually shipped. Sprint velocity based on merged PRs, not promises
No Technical Knowledge Needed
You don't need to understand Git. Tasks update automatically. Green means done. That's it
Setup in minutes.
Automation forever.
Connect your provider. Select repository. Configure sync settings. Every future branch, PR, and commit tracks automatically.
Connect Provider
Add your Personal Access Token (GitHub/GitLab) or App Password (Bitbucket). Permissions validated automatically
Select Repository
Choose which repo to connect. Webhooks created automatically for issues, commits, and PRs
Configure Sync
Enable issue sync, comment sync, commit tracking. Map workflow states. Start creating branches from tasks
GitScrum vs Alternatives
| GitScrum Git Integration | Jira + GitHub App | Asana + GitHub | |
|---|---|---|---|
| Git providers | GitHub, GitLab, Bitbucket | GitHub, Bitbucket | GitHub only |
| Branch from task | One-click | Via extension | Not supported |
| Auto-naming | -- | PROJ-123-title | Not supported |
| PR auto-linking | #TK-123 mention | Smart commits | Manual link |
| Workflow on merge | Configurable | Automation rules | Not supported |
| Issue sync | Bidirectional | One-way | Not supported |
| Notification config | 6 categories | Limited | Basic |
| Multi-provider | Simultaneous | Separate configs | Not supported |
Frequently Asked Questions
Technical details about Git integrations
Which Git providers are supported?
GitHub, GitLab, and Bitbucket. Each requires different authentication: GitHub and GitLab use Personal Access Tokens, Bitbucket uses Username + App Password. All three support branch creation, PR linking, and webhook events.
How do I create a branch from a task?
Open the task drawer. If a Git provider is connected, you'll see a Git section. Click 'Create Branch'. Branch name is auto-generated as feature/-- using your project code. Link appears in task immediately.
How does PR auto-linking work?
Include the task code anywhere in your PR title or description: #TK-123 or just TK-123. When the PR webhook fires, GitScrum extracts the code and links the PR to the task. Works for multiple task codes in one PR.
Can I connect multiple Git providers to one project?
Yes. You can connect GitHub AND GitLab to the same project. The task drawer shows a provider switcher when multiple are connected. Create branches from either provider per task.
What happens when a PR is merged?
GitScrum receives a webhook event. If the PR mentions a task code (#TK-123), the task's workflow is updated to the configured 'merge' status. You configure this per project in integration settings.
Does issue sync work bidirectionally?
Depends on configuration. You enable which direction for each event: issue created in GitHub → task created in GitScrum, issue closed in GitLab → task workflow updated. Full bidirectional requires both settings enabled.
What permissions do Personal Access Tokens need?
GitHub: repo (full repository access) and admin:repo_hook (webhook management). GitLab: api, read_repository, write_repository. These allow GitScrum to create branches, manage webhooks, and read repository data.
How do commit messages link to tasks?
Include the task code in your commit message: 'Fix login timeout #TK-847'. When the push webhook fires, GitScrum extracts TK-847 and optionally updates the task's workflow based on your commit sync settings.
Connect your Git workflow today.
GitHub, GitLab, Bitbucket—one integration. Branches from tasks. PRs auto-linked. Workflows automated. The Git integration that actually works.
No credit card required · Cancel anytime