A calm desktop timesheet for Jira Cloud.

See your Jira worklogs as a week calendar, log time with a click, and catch the days you missed before anyone has to ask.

Download Trackline All downloads

Free for macOS, Windows and Linux.

Free, MIT licensed
macOS, Windows, Linux
No account, no server

Your workweek26.5h logged · 13.5h remaining

MON098h /8h

TUE106h /8h−2h

WED118h /8h

THU124.5h /8h−3.5h

FRI130h /8h

07:0008:0009:0010:0011:0012:0013:0014:0015:0016:0017:00

OPS-31Nightly import job alerts1.5h APP-214Checkout retry banner3h WEB-87Pricing page copy review1h APP-214Checkout retry banner2.5h

APP-219Crash on empty cart2h WEB-87Pricing page copy review1h APP-214Checkout retry banner3h

DOC-12API changelog for v2.31.5h WEB-87Pricing page copy review1h APP-214Checkout retry banner1.5h APP-221Retry banner analytics events4h

APP-219Crash on empty cart3h OPS-31Nightly import job alerts1.5h 14:30

14:40

Team worklogs6 people · 148h logged in Mar 9 — Mar 13 · 10 incomplete days

Hours logged per person per day, week of March 9 (made-up data). Select a cell to see that day's worklogs.
Person	MON9	TUE10	WED11	THU12	FRI13	Total
Day total	39h	35h	39.5h	34.5h	–	148h

Team worklogs10 tickets · 148h logged in Mar 9 — Mar 13

Cost / capitalized 148h

Work type

New Features68.5h
Maintenance62h
Bug16h
Not set1.5h

Hours logged per ticket, week of March 9 (made-up data).
Ticket	Work type	Cost/Capitalized	Logged	Total logged	Logged by
APP-233Saved addresses form validationIn Progress	New Features	Capitalized	21.5h	30.5h of 24h6.5h over	AOSW
APP-214Checkout retry bannerIn Review	New Features	Capitalized	21h	27h of 32h	JWMC
WEB-87Pricing page copy reviewIn Review	Maintenance	Cost	21h	21h of 24h	LRSWMC
WEB-95Cookie banner translationsIn Progress	Maintenance	Cost	21h	23h of 24h	JWLR
WEB-91Blog index performanceIn Progress	Maintenance	Cost	17h	17h no estimate	AOLR
APP-219Crash on empty cartIn Progress	Bug	Cost	16h	16h of 8h8h over	JWMC
APP-221Retry banner analytics eventsIn Progress · in APP-214	New Features	Capitalized	15h	15h of 16h	SWMC
APP-230Order history paginationIn Progress	New Features	Capitalized	11h	11h of 16h	AO
OPS-31Nightly import job alertsDone	Maintenance	Cost	3h	3h of 4h	MC
DOC-12API changelog for v2.3In Progress	Not set	Cost	1.5h	1.5h no estimate	MC
10 tickets			148h

Replica with made-up data. Point at an hour, then click it.

Every worklog, where it actually happened.

Trackline reads your Jira worklogs and lays them out as a week or month calendar. The timeline stretches for the 07:30 start and the late fix, and entries that overlap sit side by side instead of hiding each other.

Week and month views · weekends hidden by default

Click an hour. It’s logged in Jira.

Point at the calendar and a 15-minute slot follows the cursor. Click it, then pick the issue from Recent activity or Recently viewed, or search all of Jira by summary or key. Set the duration, day, start time and a description, and the worklog is written straight to Jira.

Jira issue-type icons, so bugs still look like bugs.

The days you missed, in coral.

Turn on Focus on incomplete days and every working day below your target lights up with exactly how much is missing. Complete days and days that haven’t happened yet step back.

Your target is your workday length: 8 hours unless you change it.

Your team’s week, one grid.

Choose Jira projects and pin teammates to see people by days. Pinned people appear even when they logged nothing, which is usually the point. Click any cell to read that person’s worklogs for the day, with the same incomplete-day focus.

Try a cell on the replica.

Every ticket, costed.

Switch the team view to Tickets. Each row shows the work type, whether the work is capitalized or a cost, the hours logged this week, the total against its estimate, and who logged the time.

The bar above the table splits the week into capitalized and cost hours, so the finance question already has an answer.

Trackline finds your Work type and Cost/Capitalized fields by name. You can change them in Settings.

A CSV when someone asks for one.

Export your own worklogs, or a team summary, every worklog line and per-ticket totals as three files. They’re saved to your Downloads folder, named for the period.

trackline-team-summary-2026-03-09_2026-03-15.csv
trackline-team-worklogs-2026-03-09_2026-03-15.csv
trackline-team-tickets-2026-03-09_2026-03-15.csv

A side panel that keeps today honest.

Today’s pulse shows your hours against the target, with a one-click way to log the missing time. Needs attention lists the incomplete days. Recently worked opens the issue in Jira.

Pick a time for the daily reminder. On weekdays, if you’re below target, Trackline sends a native notification. It works while the app is running.

THURSDAY PULSE4.5h of 8h

3.5h to go · 2 entries logged today.

Log 3.5h for today

Daily reminder4:00 PM · weekdays, local time

Needs attentionThis week

Tue, Mar 102h missing

Log

Thu, Mar 123.5h missing

Log

Recently workedView all 6

APP-219Crash on empty cart

OPS-31Nightly import job alerts

APP-214Checkout retry banner

10h

APP-221Retry banner analytics events

Small things, done properly.

Week and month: A timetable of your week, or a month grid with daily totals and the issues behind them. Click the month name to jump to any month.
Overlaps side by side: Two worklogs in the same hour share the slot instead of stacking on top of each other.
A timeline that stretches: An early start or a late finish widens the hours shown, so nothing falls off the edge.
Hide weekends: On by default. Turn it off if Saturday work is part of your week.
Your workday length: Eight hours unless you say otherwise. Every target and missing-time badge follows it.
Issue-type icons: The same icons Jira uses, so a bug in the picker looks like a bug.
Light and dark: Two themes for the room you work in, and Trackline remembers your choice. The moon on the replica above switches it.
A resizable window: A native desktop window you can size and place around the rest of your work.

Your computer talks to your Jira. That’s the whole route.

Trackline has no server in the middle. Requests go straight from your machine to your Jira Cloud site, using your own Atlassian API token.

No account, no analytics. Nothing to sign up for, nothing reported back.
Your token stays in your OS vault. Built apps keep it in the system credential store, such as macOS Keychain.
Only what your account can do. Trackline sees and changes exactly what your Jira user can, nothing more.

Running in development with npm run tauri dev? Credentials are kept in a local, git-ignored file with owner-only permissions instead.

Connect Jira in three steps.

Create an API token
At id.atlassian.com → Security → API tokens.
Enter your details in Settings
Your Jira site address, your Atlassian email and the token.
Select Connect Jira
Then Refresh calendar, and the worklogs you already have load from Jira.

Download Trackline.

Pick the build for your computer. Every file comes from the latest GitHub release.

macOSApple Silicon (M1 and newer)
.dmg
macOSIntel
.dmg
WindowsWindows 10 and 11, 64-bit
Installer .msi
Linux64-bit
.AppImage .deb .rpm

Opening it the first time

Trackline isn’t signed with a paid Apple or Microsoft certificate yet, so your system asks you to confirm once.

macOS: open Trackline, then go to System Settings → Privacy & Security and select Open Anyway.
Windows: in the SmartScreen prompt, select More info → Run anyway.

After that, Trackline keeps itself up to date. It checks for new versions and asks before installing.

All releases and release notes

Or build it yourself.

Trackline is open source. Building it from source on macOS, Windows or Linux takes four commands.

Node.js 20 or newer
Rust, stable
The Tauri prerequisites for your OS

Terminal

git clone https://github.com/defrimhasani/trackline.git
cd trackline
npm install
npm run tauri dev

Want an app you can install? npm run tauri build writes a bundle to src-tauri/target/release/bundle/.

Close the week with nothing missing.

Trackline is free and MIT licensed. Issues and pull requests are welcome.

Download Trackline View on GitHub