Guide

How to log time in Jira faster

Jira logs time one entry at a time. That's fine for a single task and slow for a whole week. These are the ways to cut it down, from small habits to drafting the week at once.

The built-in way: Log work

In Jira Cloud, time goes on each work item separately:

  1. Open the work item.
  2. Select More actions (•••) → Log work, or click the Time tracking field.
  3. Enter the time spent, the date, an optional comment, and save.

If you don't see Time tracking, it is switched off for your space. Only a Jira admin can turn it on, and you need the Work on work items permission to log time.

Three things make this slow when you log after the fact:

Make the native flow quicker

Type time the way Jira reads it

Jira accepts 1h 30m, 45m or 1d. A day and a week mean however many hours your admin set as a working day and week, so check before you type 1d.

Open Log work from the keyboard

Press Ctrl + K (Cmd + K on Mac) on a work item to open Jira's command palette, then search for Log work.

Log daily, not monthly

The slow part is reconstructing what you did. Two minutes at the end of each day beats an hour of guessing at the end of the month.

Draft the whole week at once

Your Jira history already knows most of the answer: which tasks you moved to In Progress, how long they stayed there and who they were assigned to. Snaplog is a Chrome extension that turns that history into worklog drafts in a calendar:

  1. Select the days you need, a single day or a full week.
  2. Click Suggest worklogs. Empty days fill with drafts; days you already logged stay as they are.
  3. Fix anything that looks off, then Submit posts every draft to Jira.

The entries are ordinary Jira worklogs, the same as Log work creates, so Jira's own reports see them. Connecting Google Calendar or Outlook adds meetings, and GitHub adds code reviews.

When this isn't the right fit

Add Snaplog to Chrome