Quick Logger fills your Jira Log Work form’s Stage of Introduction, Description, and Fix Versions from your saved defaults — so you only ever type Time Spent by hand.
Most worklog entries share the same Stage, Description, and Fix Versions. Typing them out by hand, issue after issue, is pure friction.
Stage of Introduction
Re-typed by hand, on every single worklog entry.
Description
Copy-pasted from the last entry, if you remember to.
Fix Versions
Re-picked from a long dropdown, every time.
Filled instantly from your saved default.
Filled instantly, editable if this entry differs.
All configured versions selected in one click.
Quick Logger stays out of the way until the dialog opens — then it makes filling the form a single, deliberate click.
Watches the DOM with a MutationObserver and locates Jira's own Log Work dialog by label text — not brittle CSS classes — so it survives Jira version and theme differences.
Stage of Introduction, Description, and Fix Versions are filled the moment you click Fill Jira Log. You only ever type Time Spent.
The extension only fills fields — Jira's own validation and submit flow are untouched, so a worklog is created exactly like it always was.
Configure several Fix Versions once; every one of them is selected automatically, whether Jira renders a native select or a chip-based picker.
Re-runs detection on every DOM mutation, so it keeps working across issue navigation, modal close/reopen, and re-renders — no page reload needed.
Turn auto-fill on or off from the toolbar popup in one click, and review your saved defaults at a glance before you open Log Work.
Four steps. No configuration beyond your defaults. Works wherever Jira renders the Log Work dialog.
Quick Logger detects Jira's own Log Work dialog the moment it opens — inline, on a transition, or on the issue view.
Open the popup, click Settings, and save the Stage, Description, and Fix Versions you use most.
A small panel appears inside the dialog. One click fills all three fields, leaving Time Spent for you to type.
The worklog is created exactly like it always was — the extension never replaces or reimplements Jira's own form.
Configure them in Settings and every Log Work entry starts pre-filled — you only ever adjust what's different this time.
Stage of Introduction — where the issue originated.
A short note on the kind of work this entry covers.
One or more release versions this work applies to.
Stage: Development Description: Development / implementation work Fix Versions: Release 2.4, Release 2.5 Time Spent: 1h 30m ← the only field you typed
Still curious? Open an issue on the repo and we'll get back to you.
It's built to survive that. Fields are matched by label text, not CSS classes, so it holds up across Jira version and theme differences. If a field doesn't populate on your instance, the selectors can be adjusted.
No. Your defaults live only in chrome.storage.sync, synced across your own Chrome profile via your Google account. No network requests, no analytics, no external servers.
No. Quick Logger only fills Stage of Introduction, Description, and Fix Versions. Time Spent, validation, and submission are entirely Jira's own — untouched.
Yes. Enter them comma-separated in Settings, and every one gets selected automatically — whether Jira renders a native select or a chip-based multi-select picker.
Yes. Toggle auto-fill from the toolbar popup — the panel stops appearing until you turn it back on.
Load Quick Logger, save your Stage, Description, and Fix Versions, and every Log Work entry starts pre-filled.