Tally

Your Jira worklogs, as a timesheet you can actually read.

A browser extension for Jira Cloud. It lays out the worklogs your account can already see as a day, a week, a log and a team — and runs a stopwatch that stays in your browser until you decide to log it.

2h 15m tracked today isn’t in Jira yet.

The one number Tally keeps in front of you, from the bar at the top of every screen.

Add to Chrome Add to Edge

Free, and nothing to sign up for. Jira Cloud only.

Tally's Week view: five columns, Monday to Friday, each drawn to one shared scale and stacked in colour by issue. Above them, 47h 25m logged this week against a 40h target, 1h 35m not in Jira yet, and a banner offering to close the week.
The Week. Every day shares one scale, so a short day looks short instead of being rescaled to fill its box. The two figures above the chart are the whole argument: what you logged, and what is not in Jira yet.

See it work

Five things it does, recorded from the extension.

The names and numbers are made up. The screens are not.

The gap, always in view

Time you tracked that isn’t in Jira yet gets its own number, in amber, and stays in view until you log it or set it aside.

Tally's notice, “2 entries aren’t in Jira yet. Each one can be logged, or set aside, in the Log.”, with a Close the week button. Under it, 47h 25m logged this week of a 40h target and, in amber, 1h 35m not in Jira yet.

Track it, then log it

Stop the stopwatch and the entry waits, in amber, with a Log button that says how long. Press it, and the time is in Jira.

Tally's bar and Log, with the stopwatch running at 0:42 on NW-412. The pointer presses Stop, and the entry turns amber, Not in Jira yet, with a Log 42m button. Once that is pressed, the entry says In Jira and the bar's In Jira today goes from 0m to 42m.

Your Seven, beside the clock

Star up to seven issues and start the stopwatch on any of them from the bar. Starting one while the clock runs stops the current entry first, note included.

The menu beside Tally's running clock, headed Start on one of Your Seven, and under it, Stops NW-412 first. Five starred issues, numbered 1 to 5 in their own colours, each with its key, summary and status, the first one Running. At the foot: 2 of Your Seven are free.

Entries that repeat

Mark a worklog as repeating, and Tally offers it again on the days it repeats.

A worklog in Tally's Log: 1h 20m on NW-401, 3:00 to 4:20 PM. The pointer presses its Repeat button, and a panel opens, Repeat this entry, with Off, Weekly, Daily and Custom. Weekly is pressed, and the panel says: Repeats every Friday at 3:00 PM: 1h 20m on NW-401. Tally puts it on your Log once its time has passed, for you to log or skip. It never logs one itself.

Who logged to an epic

The Team view shows who logged time to an issue, and how much. Its child work items roll up into it, and each one opens to the people who logged to it.

Tally's Team view for NW-401, Timesheet rounding is inconsistent: 182:06 logged by seven people, each with a time and a share. The pointer opens Child work items, and the page moves down to them: On NW-401 itself, then NW-402, Round each line before the sum, 2:15. Pressed, NW-402 opens to the two people who logged to it, and the time on NW-402 itself.

What you get

Four views, and a stopwatch that survives being closed.

The Day agenda puts an hour’s work at an hour’s height, so a thin day looks thin. The Week grid totals five days at once. The Log is every entry, sortable and filterable, with the columns you choose. The Team view is for people who manage people — and it states its own blind spots rather than presenting a partial total as a complete one. And Your Seven: star up to seven issues, and the stopwatch starts on any of them from a tab beside the clock.

Tally's Day view: a Friday agenda with seven worklog blocks laid out against an hour grid from 8am to 6pm. Each block is as tall as the work took — a two-hour block is twice the height of a one-hour one — and the gaps between them are untracked time. Beside it, 10h 15m logged this day against an 8h target.
The Day. An hour of work is an hour of height, so the gaps are the untracked time rather than something you have to work out. Two things at once sit side by side.

What it does

See

  • Day, Week, Log and Team views of your existing Jira worklogs
  • Five themes, and one that follows your system’s contrast setting
  • An FAQ inside the extension: what it can see, what it sends where, what each word means

Track

  • A stopwatch that survives the browser closing, the laptop sleeping and Chrome shutting the extension down — it stores a start time, never a running counter
  • Fills in the issue key from the Jira tab you were just looking at
  • Your Seven: star up to seven issues and start the clock on any of them from the bar
  • Asks about time it counted while your machine was idle or locked, instead of silently keeping or silently trimming it
  • A keyboard shortcut, Alt+Shift+S, to start and stop without opening anything
  • An optional end-of-day reminder, off until you turn it on

Log and export

  • Log, edit and delete your own worklogs, one deliberate press at a time
  • Close the Week: everything unlogged, reviewed in the Log and put in Jira
  • Export any view to CSV or JSON — exactly the rows on screen, with the same filters applied
  • Optional rounding to a billing increment, which never changes what is stored
  • Back up and restore your stopwatch entries

What it doesn’t do

  • No account, no server, no analytics, no telemetry, no third-party code. Tally talks to your Jira site and to nothing else.
  • Nothing is written to Jira unless you press a button that says so — and only ever your own worklogs. Tally refuses to touch a colleague’s, which is stricter than Jira itself.
  • No ranking of teammates, no score against a target, no red flag beside a name.

Before you install

Three honest limits.

Worth knowing first rather than discovering later. They are the same limits the extension states on its own screens.

  • Jira Cloud only. Server and Data Center are not supported.
  • The Team view shows only what your own permissions return. Projects you cannot browse, issues under issue-level security and restricted worklogs are all absent — so Tally says so, on screen and in the export.
  • It uses your existing signed-in Jira session. If you are signed out of Jira, Tally will say so and ask you to sign in there. It never asks for your password, and there is nowhere to type one.

The first minute

  1. Install it. Nothing is asked for on the install screen beyond storage and the idle state.
  2. Have your Jira open in another tab, then open Tally from the toolbar. It offers to connect that site.
  3. Press Connect and approve access to that one atlassian.net site. Your week is on screen.

What’s new

Every release, in plain words.

What changed in each release, newest first. Older ones stay here rather than being tidied away.

1.4.0 October 2026

New

  • Entries that repeat, weekly, daily or on the days you pick.
  • Log again from a worklog’s row.
  • Your recent entries on an issue, in Log time.
  • Child work items roll up into their issue on the Team view.
  • An ✕ on each issue’s block on the Team view.
  • One date menu on every view.
  • “+ Log time” says what it does.
  • Switches in Settings.

Fixed

  • The Log’s header stays in view as you scroll.
  • The Log fits a narrow window.
  • Clearer buttons in the dark themes.

1.3.0 October 2026

New

  • Team by issue. Who logged time to an issue, and how much.
  • The bar says when Tally last fetched, and when it is fetching.
  • What you are looking at loads first.
  • Issue boxes offer what you had open in Jira.
  • Typing “PROJ-” lists that project.
  • Your Seven shows each issue’s status, and can be reordered in Settings.
  • Fields say how to type a date, a time or a length.

Fixed

  • Busy issues show every worklog.
  • Refresh re-reads older days.
  • Signed out of Jira, Tally says so.
  • Log time lists your latest issues first.
  • A new entry shows its issue at once.

1.2.0 September 2026

New

  • Number keys 1–7 open Log time on that star. A setting makes them start the stopwatch instead.
  • Help & feedback under Settings › About, with Copy diagnostics.
  • Every tooltip, dropdown and search box is Tally’s, not the browser’s.
  • T opens Log time.

Fixed

  • Tracked entries show their issue’s summary.
  • Dropdowns near the bottom open upward.
  • Search boxes clear from the keyboard.

1.1.0 September 2026

New

  • Your Seven. Star up to seven issues and start the stopwatch on any of them from the bar. Starting one while the clock runs stops the current entry first, note included.
  • One stopwatch control. Press to start, press again to stop. The small window works the same way, and has Your Seven too.
  • Day, Week and Log keep your date when you switch between them.
  • Three more themes: Paper, Graphite and high contrast. “Match my computer” follows your contrast setting too.
  • Fresh numbers when you come back, without pressing Refresh.
  • Calmer messages. One shape, one question at a time, and they can be put away.
  • Targets explain themselves and link to Settings. The ⓘ marks can be turned off.

Fixed

  • Deleting a logged entry deletes it — it no longer asks to be logged again.
  • The Tally mark shows in the light theme.
  • 60 KB smaller.

1.0.1 September 2026

New

  • A month at a time on the Team view. Week-by-week totals, plus a strip showing which days have time against them.

Fixed

  • Faster first load, most noticeably on large Jira sites.
  • The stopwatch opens one window, not a second one.
  • Short entries are caught earlier. Jira will not accept anything under a minute, so Tally says so when you stop the timer.
  • A tidier Log, and the search box shows its full placeholder.

1.0.0 September 2026

New

  • The first release. Day, Week, Log and Team views, the stopwatch, and export.

Privacy

Tally sends your data nowhere.

No Tally server, no account, no analytics, no telemetry, no crash reporting, no third-party code. The policy lists every endpoint it calls, every key it stores and every permission it asks for, with the reason for each — and it is generated from the same document the stores were given, so it cannot drift.

Read the privacy policy