Column Subscribers para Notificações | GitScrum
Configure column subscribers do GitScrum para receber notificações quando tarefas movem para colunas específicas. Saiba sobre code reviews e deploys.
4 min de leitura
How to use GitScrum column subscribers for notifications?
GitScrum column subscribers notify team members when tasks move to specific columns. Subscribe to "Code Review" to know when work needs reviewing, or "Ready to Deploy" to trigger deployments. Access column settings, add subscribers, and receive instant notifications. This reduces checking and enables faster response times.
Setting up column subscribers:
Open board settings - Click gear icon Select column - Choose target column Find subscribers section - Locate setting Add subscribers - Select team members Save configuration - Apply changes Verify - Move task to test notifications
Recommended subscriber patterns
| Column | Subscribers | Purpose |
|---|
| Code Review | Reviewers | Alert for reviews |
| Testing | QA team | Route to testers |
| Ready to Deploy | DevOps | Trigger deployment |
| Blocked | Tech lead | Escalation |
| Done | Product owner | Completion visibility |
Subscriber benefits
| Benefit | Impact |
|---|
| No constant checking | Notifications come to you |
| Faster response | Instant awareness |
| Clear responsibility | Know when to act |
| Reduced delays | No waiting for notice |
| Team alignment | Everyone informed |
Column subscribers vs task assignment
| Aspect | Column Subscribers | Task Assignment |
|---|
| Scope | Column-wide | Single task |
| Trigger | Task enters column | Manual assign |
| Notification | Column-based | Task-based |
| Use case | Role-based alerts | Ownership |
Common subscription patterns
| Team Role | Subscribe To |
|---|
| Senior Developer | Code Review |
| QA Engineer | Testing, QA Review |
| DevOps | Ready to Deploy, Production |
| Tech Lead | Blocked, Critical |
| Product Owner | Done, Released |
Subscription workflow
| Event | Action |
|---|
| Developer finishes task | Moves to Code Review |
| Reviewer notified | Gets instant alert |
| Reviewer acts | Reviews code |
| Moves to Testing | QA notified |
| QA approves | Moves to Deploy |
| DevOps notified | Handles deployment |
Best practices
| Practice | Reason |
|---|
| Subscribe to your responsibility | Get relevant alerts |
| Avoid over-subscribing | Notification fatigue |
| Combine with auto-assign | Double coverage |
| Review subscriptions periodically | Keep current |
| Use for bottleneck columns | Fast response needed |
Notification channels
| Channel | When |
|---|
| In-app | Always available |
| Email | Optional setting |
| Slack/Teams | Via integration |
| Mobile push | App installed |
Troubleshooting subscriptions
| Issue | Solution |
|---|
| No notifications | Check subscription settings |
| Too many notifications | Reduce columns subscribed |
| Wrong people notified | Review subscriber list |
| Delayed notifications | Check notification settings |
Related articles
