---

name: "jira-time-tracking" description: "Time tracking and worklog management with estimation, reporting, and billing integration. Use for logging work, managing estimates, generating reports, bulk operations, and team time tracking policies." version: "1.0.0" author: "jira-assistant-skills" license: "MIT" allowed-tools: ["Bash", "Read", "Glob", "Grep"]

JIRA Time Tracking Skill

Risk Levels

Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible

When to use this skill

Use the jira-time skill when you need to:

• Log time spent working on JIRA issues
• View, update, or delete work log entries
• Set or update time estimates (original and remaining)
• Generate time reports for billing, invoicing, or tracking
• Export timesheets to CSV or JSON format
• Bulk log time across multiple issues

What this skill does

IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.

The jira-time skill provides comprehensive time tracking and worklog management:

Worklog Management

• Add worklogs - Log time with optional comments and date/time
• View worklogs - List all time entries for an issue
• Update worklogs - Modify existing time entries
• Delete worklogs - Remove time entries with estimate adjustment

Time Estimates

• Set estimates - Configure original and remaining estimates
• View time tracking - See complete time tracking summary with progress

Reporting

• Time reports - Generate reports by user, project, or date range
• Export timesheets - Export to CSV/JSON for billing systems
• Bulk operations - Log time to multiple issues at once

Available Commands

All commands support --help for full documentation.

Common Options

All commands support these common options:

Worklog-specific options

Report-specific options

Exit Codes

All commands return standard exit codes:

Examples

Log time to an issue

Copy# Log 2 hours of work
jira-as time log PROJ-123 --time 2h

# Log time with a comment
jira-as time log PROJ-123 --time "1d 4h" --comment "Debugging authentication issue"

# Log time for yesterday
jira-as time log PROJ-123 --time 2h --started yesterday

# Log time without adjusting estimate
jira-as time log PROJ-123 --time 2h --adjust-estimate leave

View worklogs

Copy# List all worklogs for an issue
jira-as time worklogs PROJ-123

# Filter by author
jira-as time worklogs PROJ-123 --author currentUser()

# Filter by date range
jira-as time worklogs PROJ-123 --since 2025-01-01 --until 2025-01-31

# Output as JSON
jira-as time worklogs PROJ-123 --output json

Manage estimates

Copy# Set original estimate
jira-as time estimate PROJ-123 --original "2d"

# Set remaining estimate
jira-as time estimate PROJ-123 --remaining "1d 4h"

# View time tracking summary
jira-as time tracking PROJ-123

Generate reports

Copy# My time for last week
jira-as time report --user currentUser() --period last-week

# Project time for this month
jira-as time report --project PROJ --period this-month

# Export to CSV for billing
jira-as time report --project PROJ --since 2025-01-01 --until 2025-01-31 --format csv > timesheet.csv

# Group by day for daily summary
jira-as time report --project PROJ --period this-week --group-by day

# Group by user for team summary
jira-as time report --project PROJ --period this-month --group-by user --format json

Export timesheets

Copy# Export last month's timesheets to CSV
jira-as time export --project PROJ --period last-month --output timesheets.csv

# Export to JSON for integration
jira-as time export --project PROJ --since 2025-01-01 --until 2025-01-31 --format json

# Export user's timesheets for billing
jira-as time export --user alice@company.com --period this-month --output billing.csv

Bulk operations

Copy# Preview bulk time logging (dry run)
jira-as time bulk-log --issues PROJ-1,PROJ-2,PROJ-3 --time 15m --comment "Sprint planning" --dry-run

# Log standup time to multiple issues
jira-as time bulk-log --issues PROJ-1,PROJ-2,PROJ-3 --time 15m --comment "Sprint planning"

# Log time to JQL results with dry run
jira-as time bulk-log --jql "sprint = 456" --time 15m --comment "Daily standup" --dry-run

# Execute after confirming dry run output
jira-as time bulk-log --jql "sprint = 456" --time 15m --comment "Daily standup"

Delete worklogs

Copy# Preview worklog deletion (dry run)
jira-as time delete-worklog PROJ-123 --worklog-id 12345 --dry-run

# Delete with automatic estimate adjustment
jira-as time delete-worklog PROJ-123 --worklog-id 12345 --adjust-estimate auto

# Delete without modifying estimate
jira-as time delete-worklog PROJ-123 --worklog-id 12345 --adjust-estimate leave

# Delete without confirmation prompt
jira-as time delete-worklog PROJ-123 --worklog-id 12345 --yes

Dry Run Support

The following commands support --dry-run for previewing changes without making modifications:

Dry-Run Pattern: Always use --dry-run first when performing bulk operations or deleting worklogs. This preview-before-execute workflow prevents accidental data changes:

Copy# Step 1: Preview the operation
jira-as time bulk-log --jql "sprint = 456" --time 15m --dry-run

# Step 2: Review the output carefully
# Step 3: Execute only after confirming the preview is correct
jira-as time bulk-log --jql "sprint = 456" --time 15m --comment "Daily standup"

Time format

JIRA accepts human-readable time formats:

• 30m - 30 minutes
• 2h - 2 hours
• 1d - 1 day (8 hours by default)
• 1w - 1 week (5 days by default)
• 2d 4h 30m - Combined format

Configuration

Time tracking must be enabled in your JIRA project. If you receive an error about time tracking being disabled, ask your JIRA administrator to enable it.

Troubleshooting

Common Issues

"Time tracking is not enabled"

Time tracking must be enabled at the project level. Contact your JIRA administrator to enable it in Project Settings > Features > Time Tracking.

"Cannot log time to this issue"

Possible causes:

• The issue is in a status that doesn't allow time logging
• You don't have permission to log work on this issue
• The issue type doesn't support time tracking

"Worklog not found"

The worklog ID may be incorrect or the worklog was already deleted. Use jira-as time worklogs ISSUE-KEY to list valid worklog IDs.

Estimates not updating correctly

JIRA Cloud has a known bug (JRACLOUD-67539) where estimates may not update as expected. Workaround: Set both original and remaining estimates together:

Copyjira-as time estimate PROJ-123 --original "2d" --remaining "1d"

Time logged but not showing in reports

• Check the --started date - worklogs are associated with the start date, not creation date
• Verify the correct --period filter is being used
• Ensure the user has permission to view the issue's worklogs

"Invalid time format"

Use JIRA's standard time notation:

• Correct: 2h, 1d 4h, 30m, 1w 2d
• Incorrect: 2 hours, 1.5h, 90 minutes

Bulk operation failures

When using bulk time logging:

1. Always use --dry-run first to preview changes
2. Check that all issues in the JQL results are accessible
3. Verify time tracking is enabled on all target projects

Permission Requirements

To use time tracking features, you typically need:

• Browse Projects - View issues and worklogs
• Work On Issues - Add worklogs to issues
• Edit All Worklogs - Modify/delete any user's worklogs (admin)
• Delete All Worklogs - Delete any user's worklogs (admin)

For detailed permission matrix, see Permission Matrix.

Advanced Troubleshooting

API rate limits

When performing bulk operations on large result sets, the CLI automatically retries with exponential backoff on 429 errors. To reduce load:

• Use smaller date ranges for reports
• Filter JQL to limit results before bulk operations

Timezone issues

Worklogs use UTC internally. If time appears on wrong date:

• Check your JIRA timezone settings
• Use explicit --started date when needed

Bulk operation timeouts

Large JQL result sets may timeout:

Copy# Use smaller batches instead of one large query
jira-as time bulk-log --issues PROJ-1,PROJ-2,PROJ-3 --time 15m

Worklog visibility issues

If worklogs are logged but others cannot see them:

• Check worklog visibility settings
• Verify issue security scheme permissions

For complete error code reference, see Error Codes.

Common Questions

Why is my estimate not updating? JIRA Cloud bug (JRACLOUD-67539). Set both estimates together:

Copyjira-as time estimate PROJ-123 --original "2d" --remaining "1d 4h"

How do I log time for someone else? You need "Edit All Worklogs" permission. Most users can only log their own time.

Can I bill partial hours? Yes. Use minutes for precision: 1h 45m (not 1.75h). JIRA doesn't support decimal hours.

How does --adjust-estimate work?

Advanced Guides

For specific roles and use cases, see:

Quick Reference

Best Practices

For comprehensive guidance on time logging workflows, estimate management, and reporting patterns, see Best Practices Guide (navigation hub to all guides).

Related skills

• jira-issue: Create and manage issues (can set estimates on creation)
• jira-search: Search issues and view time tracking fields
• jira-agile: Sprint management with time tracking integration
• jira-bulk: Bulk operations at scale with dry-run support