GitScrum
Try free
6 min read • Guide 201 of 877

Integrating GitScrum with Slack

GitScrum's Slack integration bridges project management and team communication. Get notifications where you work, create tasks without context switching, and keep discussions linked to the work they reference.

Integration Benefits

Without IntegrationWith Integration
Switch apps for updatesNotifications in Slack
Copy/paste to create tasksSlash command creates task
Discussions disconnectedLinked to tasks
Delayed awarenessReal-time alerts

Setup

Connecting Slack

INTEGRATION SETUP
═════════════════

STEP 1: Authorize
─────────────────────────────────────
GitScrum → Settings → Integrations → Slack
Click "Add to Slack"
Select workspace
Authorize GitScrum app
Choose default channel

STEP 2: Configure Channels
─────────────────────────────────────
Project notifications:
├── #project-alpha → Project Alpha updates
├── #project-beta → Project Beta updates
├── #dev-team → Team-wide alerts
└── Direct messages → Personal notifications

STEP 3: Choose Events
─────────────────────────────────────
Per channel, enable:
├── Task created
├── Task completed
├── Task assigned to you
├── Comment added
├── Blocker flagged
├── Sprint started/ended
├── @mentions
└── Due date reminders

STEP 4: Test
─────────────────────────────────────
Create a test task
Verify notification appears in Slack
Adjust settings as needed

Notification Configuration

NOTIFICATION SETTINGS
═════════════════════

CHANNEL NOTIFICATIONS:
─────────────────────────────────────
#project-alpha receives:
├── ✅ New tasks created
├── ✅ Tasks completed
├── ✅ Blockers flagged
├── ✅ Sprint started/ended
├── ❌ Individual comments (too noisy)
├── ❌ Status changes (too noisy)
└── ❌ Assignments (personal, use DM)

DIRECT MESSAGES receive:
├── ✅ Assigned to me
├── ✅ @mentioned
├── ✅ My task commented
├── ✅ Due date reminders
├── ✅ Blocked items I own
└── ❌ Team-wide events

DIGEST OPTIONS:
├── Real-time: Immediate notification
├── Hourly: Bundled every hour
├── Daily: Morning summary at 9am
└── Configure per notification type

Slack Commands

Creating Tasks

TASK CREATION FROM SLACK
════════════════════════

QUICK CREATE:
─────────────────────────────────────
/gitscrum create Fix login button on mobile

Result:
GitScrum Bot: ✅ Task created: GS-456
"Fix login button on mobile"
Project: Default | Assignee: You
[View in GitScrum]

WITH DETAILS:
─────────────────────────────────────
/gitscrum create "Add user avatars" 
  --project "Customer Portal"
  --assign @sarah
  --priority high
  --label feature

Result:
GitScrum Bot: ✅ Task created: GS-457
"Add user avatars"
Project: Customer Portal | Assignee: Sarah
Priority: High | Labels: feature
[View in GitScrum]

FROM MESSAGE:
─────────────────────────────────────
Right-click any Slack message
→ "More actions"
→ "Create GitScrum Task"

Message content becomes task description
Original message linked

Status Commands

SLACK COMMANDS
══════════════

CHECK STATUS:
─────────────────────────────────────
/gitscrum status GS-456

Result:
GitScrum Bot:
GS-456: Fix login button on mobile
Status: In Progress
Assignee: Sarah
Sprint: Sprint 8
Updated: 2 hours ago
[View in GitScrum]

MY TASKS:
─────────────────────────────────────
/gitscrum mine

Result:
GitScrum Bot:
Your tasks (4):
• GS-456 - Fix login button [In Progress]
• GS-458 - API documentation [Ready]
• GS-461 - Code review [Review]
• GS-462 - Update tests [Ready]
[View board]

SPRINT STATUS:
─────────────────────────────────────
/gitscrum sprint

Result:
GitScrum Bot:
Sprint 8 (Day 6 of 10)
Progress: ████████░░░░ 65%
Completed: 16/25 items
Blocked: 1 item
[View sprint]

Notification Examples

Task Notifications

SAMPLE NOTIFICATIONS
════════════════════

TASK CREATED:
─────────────────────────────────────
GitScrum Bot → #project-alpha

📋 New task created
GS-460: Implement payment retry logic

Created by: Mike
Priority: High
Labels: backend, payments
[View task] [Assign to me]

TASK COMPLETED:
─────────────────────────────────────
GitScrum Bot → #project-alpha

✅ Task completed
GS-455: User profile API

Completed by: Sarah
Time: 6h 30m
Sprint: 8
[View task]

BLOCKER:
─────────────────────────────────────
GitScrum Bot → #project-alpha

🔴 Task blocked
GS-456: Fix login button on mobile

Blocked by: Sarah
Reason: "Need API credentials from vendor"
Duration: 4 hours
[View task] [Help unblock]

Personal Notifications

PERSONAL DM NOTIFICATIONS
═════════════════════════

ASSIGNED TO YOU:
─────────────────────────────────────
GitScrum Bot → DM

📌 Task assigned to you
GS-465: Add rate limiting

Assigned by: Mike
Priority: Medium
Sprint: 8
Due: Friday
[View task] [Start work]

MENTIONED:
─────────────────────────────────────
GitScrum Bot → DM

👋 You were mentioned
GS-460: Implement payment retry logic

Mike commented:
"@sarah can you review the approach
before I start implementation?"
[View comment] [Reply]

DUE REMINDER:
─────────────────────────────────────
GitScrum Bot → DM

⏰ Due tomorrow
GS-455: User profile API

Status: In Progress
Assignee: You
Due: Tomorrow, 5pm
[View task] [Mark complete]

Best Practices

Slack Integration Tips

INTEGRATION BEST PRACTICES
══════════════════════════

CHANNEL ORGANIZATION:
├── #proj-[name] → Project-specific updates
├── #dev-team → Team-wide alerts
├── #blockers → All blocked items (quick response)
└── DMs → Personal assignments and mentions

AVOID NOISE:
├── Don't send every status change to channel
├── Use DMs for personal notifications
├── Disable low-value notifications
├── Use digest for non-urgent
└── Test before broad rollout

CONVERSATION LINKING:
├── Discuss in Slack for quick chat
├── Move decisions to GitScrum comments
├── Reference tasks with ID in Slack
├── Link task when discussion happens
└── Don't duplicate information

SLASH COMMAND TRAINING:
├── Share command reference with team
├── Encourage /gitscrum create usage
├── Faster than opening app
└── Context preserved

Integration Workflow

DAILY WORKFLOW WITH SLACK
═════════════════════════

MORNING:
├── Check DMs for assignments/mentions
├── /gitscrum mine to see today's work
├── Acknowledge notifications

DURING DAY:
├── Notifications appear as you work
├── Create tasks from Slack when needed
├── Discuss in thread, link to task
├── Update status in GitScrum

BLOCKING:
├── Blocker notification to channel
├── Team sees and helps
├── Quick resolution
├── Less stuck time

END OF DAY:
├── Any pending DM notifications
├── Update task status
├── Team sees progress in channel

Best Practices

For Slack Integration

  1. Configure thoughtfully — Not everything to every channel
  2. Use DMs for personal — Assignments, mentions to you
  3. Channels for team — Completions, blockers, sprints
  4. Link discussions — Connect Slack to tasks
  5. Train team on commands — /gitscrum saves time

Anti-Patterns

INTEGRATION MISTAKES:
✗ All notifications to one channel (noise)
✗ No notifications (missed info)
✗ Discussions in Slack only (lost context)
✗ Ignoring slash commands (missed efficiency)
✗ Too many channels (fragmentation)
✗ Real-time for everything (interruptions)
✗ No DM notifications (missed assignments)
Back to How To Guides