Slack Integration | Smart Channel Routing Setup
Connect GitScrum to Slack for task updates, assignments, and due dates. Route notifications to specific channels. Use digests to prevent notification fatigue.
6 min read
Email notifications get buried. GitScrum's Slack integration puts project updates where your team already works. With smart channel routing and customizable notifications, you can ensure the right information reaches the right people without notification fatigue.
Why Slack Integration
| Email Notifications | Slack Integration |
|---|---|
| Delayed checking | Real-time updates |
| Lost in inbox | Visible in flow |
| No context | Thread discussions |
| One-way | Interactive commands |
| Individual | Team visibility |
Setup Process
App Installation
SLACK INTEGRATION SETUP
═══════════════════════
STEP 1: Install App
─────────────────────────────────────
GitScrum Settings → Integrations → Slack
Click "Add to Slack"
Select your workspace
Authorize permissions
STEP 2: Connect Channels
─────────────────────────────────────
Invite @GitScrum to channels
/invite @gitscrum
STEP 3: Configure Notifications
─────────────────────────────────────
Map events to channels
Set notification levels
Test connections
PERMISSIONS REQUIRED:
├── Send messages
├── Read channel history
├── Post in channels
├── Direct messages
└── Slash commands
Channel Strategy
CHANNEL MAPPING STRATEGY
════════════════════════
PROJECT CHANNELS:
├── #project-website → Website project notifications
├── #project-mobile → Mobile app project notifications
└── #project-api → API project notifications
TEAM CHANNELS:
├── #team-frontend → Frontend team tasks
├── #team-backend → Backend team tasks
└── #team-design → Design team tasks
SPECIAL CHANNELS:
├── #releases → Deploy and release notifications
├── #critical-bugs → Priority:critical bugs only
├── #standup → Daily async standups
└── #wins → Completed milestone celebrations
Notification Configuration
Event Mapping
NOTIFICATION RULES
══════════════════
PROJECT → CHANNEL RULES:
Website Project → #project-website:
├── ✓ Task created
├── ✓ Status changed
├── ✓ Assignment changed
├── ✗ Comments (too noisy)
├── ✓ Sprint started/ended
└── ✓ Milestone completed
ALL PROJECTS → #critical-bugs:
├── Condition: label = "priority:critical"
├── Events: Created, status changed
└── Alert: @channel mention
ALL PROJECTS → #releases:
├── Condition: label = "release"
├── Events: Task completed
└── Include: Release notes link
Notification Format
SLACK MESSAGE FORMATS
═════════════════════
TASK CREATED:
┌─────────────────────────────────────────────────┐
│ 📋 New Task Created │
│ │
│ *GS-456: Implement user authentication* │
│ Project: Website Redesign │
│ Priority: High │
│ Assigned to: @sarah │
│ │
│ [View Task] [Quick Actions ▾] │
└─────────────────────────────────────────────────┘
STATUS CHANGED:
┌─────────────────────────────────────────────────┐
│ ✓ Task Status Updated │
│ │
│ *GS-456* moved to *In Review* │
│ by @mike │
│ │
│ [View Task] │
└─────────────────────────────────────────────────┘
DAILY DIGEST:
┌─────────────────────────────────────────────────┐
│ 📊 Daily Summary: March 15 │
│ │
│ Completed: 8 tasks │
│ Created: 12 tasks │
│ In Review: 5 tasks │
│ Blocked: 2 tasks ⚠️ │
│ │
│ Sprint Progress: 65% │
│ │
│ [View Dashboard] │
└─────────────────────────────────────────────────┘
Slash Commands
Available Commands
GITSCRUM SLASH COMMANDS
═══════════════════════
TASK COMMANDS:
├── /gs create [title]
│ Create new task quickly
│
├── /gs search [query]
│ Find tasks matching query
│
├── /gs assign [task-id] @user
│ Assign task to user
│
└── /gs status [task-id] [status]
Update task status
INFO COMMANDS:
├── /gs my
│ Show my open tasks
│
├── /gs sprint
│ Current sprint summary
│
├── /gs standup
│ Start async standup
│
└── /gs help
Show all commands
EXAMPLES:
─────────────────────────────────────
/gs create Fix login button styling
→ Creates task, returns link
/gs my
→ Lists your 5 most recent tasks
/gs sprint
→ Shows sprint progress and stats
─────────────────────────────────────
Interactive Actions
SLACK INTERACTIVE FEATURES
══════════════════════════
QUICK ACTIONS (from message):
┌─────────────────────────────────────────────────┐
│ 📋 GS-456: User authentication │
│ Status: In Progress │
│ │
│ [Start Timer] [Mark Done] [Add Comment] │
│ [Assign ▾] [Priority ▾] [More ▾] │
└─────────────────────────────────────────────────┘
CREATE FROM MESSAGE:
1. Hover over any Slack message
2. Click "..." → "Create GitScrum Task"
3. Task created with message as description
4. Link posted to thread
THREAD → COMMENTS:
├── Reply in Slack thread
├── Option to sync to task
├── Two-way comment sync
└── Context preserved
Async Standups
Standup Configuration
ASYNC STANDUP SETUP
═══════════════════
SCHEDULE:
├── Days: Mon-Fri
├── Time: 9:00 AM (local)
├── Channel: #standup
└── Reminder: 15 min before
QUESTIONS:
├── What did you accomplish yesterday?
├── What are you working on today?
├── Any blockers?
└── (Optional) How are you feeling?
STANDUP MESSAGE:
┌─────────────────────────────────────────────────┐
│ 📅 Daily Standup - March 15 │
│ │
│ Good morning team! Time for standup. │
│ │
│ Please share: │
│ 1. Yesterday's accomplishments │
│ 2. Today's plan │
│ 3. Any blockers │
│ │
│ [Start My Update] │
│ │
│ Responses: 0/8 │
└─────────────────────────────────────────────────┘
Best Practices
For Slack Notifications
Noise Management
REDUCING NOTIFICATION NOISE
═══════════════════════════
INSTEAD OF: DO THIS:
─────────────────────────────────────────────
All events → #team Project → project channel
Every comment → channel Comments → thread only
Real-time everything Daily digest for low priority
@channel on all @channel only for critical
Everyone sees everything Role-based subscriptions
Anti-Patterns
SLACK INTEGRATION MISTAKES:
✗ All notifications to one channel
✗ @channel for everything
✗ No digest option
✗ Ignoring thread features
✗ Not training slash commands
✗ Too many notification types
✗ No channel strategy