Skip to main content

Overview

This page provides practical examples of how to use Slack time tracking commands in real-world scenarios. Each example includes the command, context, and expected outcome.

Simple Time Tracking

Basic Timer Operations

/timetracker start description:"Working on documentation"

Manual Time Logging

/timetracker log 1.5

Project-Based Tracking

Client Work Examples

/timetracker start project:"ACME Corp Website" description:"Homepage redesign"

Internal Work Examples

/timetracker start project:"Internal Tools" description:"API development"

Meeting and Collaboration

Meeting Time Tracking

/timetracker start description:"Daily standup meeting"

Collaboration Examples

/timetracker start project:"Internal Tools" task:"Code Review" description:"Reviewing pull requests"

Development Workflows

Feature Development

/timetracker start project:"E-commerce Platform" task:"User Authentication" description:"Implementing OAuth"

Bug Fixes

/timetracker start project:"Client Website" task:"Bug Fixes" description:"Fixing responsive layout issues"

Advanced Usage Scenarios

Complex Project Tracking

/timetracker start project:"Marketing Campaign" task:"Social Media" description:"Instagram campaign planning" tags:"urgent,social,planning"

Multi-Project Day

/timetracker start project:"ACME Corp" description:"Morning client work"

Real-World Workflows

Daily Routine Example

Morning Setup:
/timetracker start project:"ACME Corp Website" description:"Daily client work"
Lunch Break:
/timetracker stop
Afternoon Work:
/timetracker start project:"Internal Tools" description:"Internal development"
End of Day:
/timetracker stop
/timetracker status

Weekly Planning Example

Monday - Project Planning:
/timetracker start project:"ACME Corp Website" task:"Planning" description:"Sprint planning and requirements"
Tuesday - Development:
/timetracker start project:"ACME Corp Website" task:"Development" description:"Feature implementation"
Wednesday - Testing:
/timetracker start project:"ACME Corp Website" task:"Testing" description:"QA and bug fixes"
Thursday - Client Communication:
/timetracker start project:"ACME Corp Website" task:"Communication" description:"Client updates and feedback"
Friday - Documentation:
/timetracker start project:"ACME Corp Website" task:"Documentation" description:"Project documentation and handoff"

Emergency Response Example

Urgent Bug Report:
/timetracker start project:"Production System" task:"Emergency Fix" description:"Critical bug in payment system" tags:"urgent,production,bugfix"
After Fix:
/timetracker stop
/timetracker log 0.5 project:"Production System" task:"Emergency Fix" description:"Hotfix deployment and verification" tags:"urgent,deployment"

Best Practice Examples

Descriptive Commands

/timetracker start project:"Client Website" description:"Implementing user dashboard with real-time data"

Proper Project Organization

/timetracker start project:"ACME Corp Website" task:"User Dashboard" description:"Adding data visualization components"

Effective Tag Usage

/timetracker log 3.0 project:"Development" description:"API optimization" tags:"performance,backend,optimization"

Common Patterns

Quick Time Logging

For retrospective time logging at the end of the day:
# Morning work
/timetracker log 2.0 project:"Client A" description:"Morning development work"

# Meeting
/timetracker log 1.0 project:"Client A" description:"Requirements meeting" tags:"meeting"

# Afternoon work
/timetracker log 3.5 project:"Client A" description:"Afternoon development and testing"

Project Switching

When switching between projects during the day:
# Stop current timer
/timetracker stop

# Start new project
/timetracker start project:"Client B" description:"Switching to new project work"

Status Checking

Regular status checks to stay aware of time:
# Check current status
/timetracker status

# See recent entries and current timer

What’s Next?