Jira Tempo

This launches a 4-step interactive wizard requiring user input:

1. Jira Profile URL — Click your avatar in Jira → Profile → Copy the URL
2. Atlassian User Email — Your Jira/Atlassian account email
3. Atlassian API Token — Generate at https://id.atlassian.com/manage-profile/security/api-tokens
4. Tempo API Token — Generate at https://{yourCompany}.atlassian.net/plugins/servlet/ac/io.tempo.jira/tempo-app#!/configuration/api-integration

⚠️ Note: The setup command opens browser windows for token generation and requires interactive prompts. It cannot be automated.

Quick Reference

Log Time

Duration format: 1h, 30m, 1h30m, 90m Interval format: 09:00-17:00, 9-17, 09:30-12:15

Basic logging:

# Log 2 hours to PROJ-123 today
tempo log PROJ-123 2h

# Shorthand
tempo l PROJ-123 2h

Log with time range:

# Log from 9 AM to 5 PM (8 hours)
tempo log PROJ-123 09:00-17:00

# Log from 1:30 PM to 3:00 PM (90 minutes)
tempo log PROJ-123 13:30-15:00

Log to a specific date:

# Yesterday
tempo log PROJ-123 1h y
tempo log PROJ-123 1h yesterday

# Specific date
tempo log PROJ-123 2h 2024-01-15

With description and custom start:

# Add a description
tempo log PROJ-123 1h -d "Reviewed PR #456"

# Specify start time when using duration
tempo log PROJ-123 2h -s 10:00

List Worklogs

View today's logged time:

tempo list
tempo ls

View specific dates:

# Yesterday
tempo list y

# Specific date
tempo list 2024-01-15

Verbose output (with descriptions):

tempo list -v

Output includes:

• Monthly progress (e.g., "120/132h")
• Daily worklogs with IDs, times, issues, and durations
• Required hours vs logged hours per day

Delete Worklogs

Use worklog IDs from tempo list output.

Delete single worklog:

tempo delete 123456
tempo d 123456

Delete multiple:

tempo delete 123456 123457 123458

Time Tracker

Track time in real-time and log when done.

Start tracking:

tempo tracker:start PROJ-123
tempo start PROJ-123

# With description
tempo start PROJ-123 -d "Working on feature X"

# Stop previous tracker on same issue if exists
tempo start PROJ-123 --stop-previous

Pause/Resume tracking:

tempo tracker:pause PROJ-123
tempo pause PROJ-123

tempo tracker:resume PROJ-123
tempo resume PROJ-123

Stop and log time:

tempo tracker:stop PROJ-123
tempo stop PROJ-123

# With description
tempo stop PROJ-123 -d "Completed implementation"

Manage trackers:

# List all active/paused trackers
tempo tracker:list

# Delete a tracker without logging
tempo tracker:delete PROJ-123

Aliases

Aliases let you use short names instead of full issue keys.

Set an alias:

tempo alias:set lunch BREAK-001
tempo alias:set standup MEET-123

Use aliases in commands:

tempo log lunch 30m
tempo start standup
tempo stop standup -d "Daily standup"

Manage aliases:

# List all aliases
tempo alias:list

# Delete an alias
tempo alias:delete lunch

Common Workflows

Log a full workday:

# Morning work
tempo log PROJ-123 09:00-12:00 -d "Feature development"

# Lunch
tempo log lunch 30m

# Afternoon work
tempo log PROJ-123 13:00-17:00 -d "Code review and testing"

# Verify
tempo ls

Track and log using timer:

# Start working on ticket
tempo start PROJ-456 -d "Bug investigation"

# ... work ...

# Finish and log
tempo stop PROJ-456 -d "Fixed null pointer issue"

Fix a mistaken entry:

# Find the worklog ID
tempo ls

# Delete it
tempo d 123456

# Re-log with correct details
tempo log PROJ-123 1h -d "Corrected description"

Safety Guidelines

ALWAYS:

• Verify worklog with tempo ls after logging
• Get confirmation before deleting worklogs
• Show the exact command before executing destructive operations

NEVER:

• Delete worklogs without showing user what will be deleted
• Assume date formats — confirm with user if ambiguous
• Bulk delete without explicit approval

Error Handling

"tempo: command not found" → tempomat not installed. Run: npm install -g tempomat, then run tempo setup manually (interactive).

"Authentication failed" or API errors → Tokens may be expired. User must run tempo setup manually (interactive) to reconfigure.

"Issue not found" → Check issue key exists and user has access. Try: jira issue view ISSUE-KEY

Triggers

• "log 2 hours to PROJ-123"
• "book time for ticket ABC-456"
• "show my timesheet for today"
• "delete my worklog from yesterday"
• "start tracking time on PROJ-789"
• "what did I log today?"
• "log 30m for lunch to BREAK-001"