Jira / time tracking / screenshots

Time tracking
for Jira.

Track Jira work from your desktop. Time syncs to Jira in real time — with optional screenshots, cost and MCP access.

Start tracking time
jira / WIN-28 / live session tracking
Current Jira issue
Review Bandanaut website
00:00:00
Jira synced Screenshots on
01 / DESKTOP TRACKING

Track Jira work with screenshots.

Managers can capture a screenshot every 10 minutes — or turn screenshots off completely.

02 / JIRA + MCP

Jira-native. Built for MCP.

Time syncs into Jira worklogs as you track, with MCP access when you need custom analysis.

03 / COST CONTROL

Know what the work costs.

Assign hourly rates, review tracked time, and see labour cost across the work your team is doing.

01 / Native Jira time tracking

Works natively in Jira.

Track from Mac or Windows. Pick a Jira issue. The worklog updates as you work.

Start tracking time
Jira / WIN-28worklog / live
WIN-28
Review Bandanaut website
In progress Assignee · Bertrams Tracked · live
Bandanaut desktopJira worklog
current Jira issue● IN
00:42:18
02 / Screenshots

Optional screenshots.

Managers can capture a screenshot every 10 minutes while time is tracked — or disable screenshots completely.

Start tracking time
Bandanaut / screenshotsWIN-28 · 14:00–15:00
14:07
14:18
14:29
14:41
14:52
15:00
6 screenshots / 1h trackedactivity · 74%
03 / Reports, cost & MCP

See cost. Ask anything.

Add hourly rates, review the numbers in Bandanaut, or query the same data through MCP.

Start tracking time
Bandanaut / operating viewthis week
Tracked time
173.6h
Across 11 people and 42 Jira issues.
Labour cost
$4,980
At an average effective rate of ~$28.70/hr.
Bandanaut MCP● connected
> What did WIN cost us this week, and where did the time go?
$1,742.40 across 58.1 tracked hours.
Desktop app: 22.4h · Screenshots: 14.8h · Jira sync: 11.6h · Other: 9.3h.
04 / How it works

How it works.

Install. Pick a Jira issue. Start tracking. Jira updates automatically.

01 / Install

Install

Add Bandanaut to Jira.

02 / Desktop

Desktop

Open the Mac or Windows app.

03 / Select

Pick

Choose the Jira issue.

04 / Start

Start tracking.

Time, activity and optional screenshots begin recording.

05 / Auto-sync

Auto-sync to Jira.

Worklogs update as the timer runs.

Start tracking time
05 / Comparison

Why Bandanaut?

Standalone trackers can capture screenshots but treat Jira as an integration. Jira-native trackers live inside Jira but do not provide desktop screenshots.

Standalone time trackers

Standalone time trackers

✓Screenshots
✕Real-time Jira sync
✕Native Jira tracking
Jira is an integration. Time is written back later.
→
Bandanaut

Bandanaut

✓Screenshots
✓Real-time Jira sync
✓Native Jira tracking
Track the Jira issue itself. Worklogs update as you track.
←
Jira-native time trackers

Jira-native time trackers

✕Screenshots
✓Native Jira tracking
✓Jira worklogs
Built inside Jira, but without desktop screenshot tracking.
Start tracking time
Remote team
Offshore hiring
Jira-based
Built from use
06 / Built from the problem

Built by a remote team that actually works this way.

We run a distributed team and hire offshore ourselves. Jira is where the work lives, but the management data around that work was always fragmented.

Standalone trackers gave us screenshots but treated Jira like an integration. Jira-native trackers gave us worklogs but not the visibility we needed around the actual work.

So we built Bandanaut around the way we actually manage a remote team: real-time Jira sync, optional screenshots, time approval, labour cost, and direct access to the data when the built-in views are not enough.

Start tracking time
07 / Product principles

The principles Bandanaut is built on.

These are the product decisions we keep coming back to.

01 / Project management

Time tracking belongs inside strong project management.

Jira is powerful enough to run complex work. Time tracking should sit directly on top of it, not force teams into a weaker parallel system.

02 / Cost

Hours are only half the answer.

Tracked time should tell you what the work actually costs — across people, projects and the work being delivered.

03 / Strong defaults

Answer the obvious questions by default.

Managers should not need to build a reporting system just to understand time, screenshots, approvals and cost.

04 / MCP

Do not trap the data in the interface.

The built-in UI should be useful on its own, but the same data should also be available through MCP for custom questions and workflows.

08 / FAQ

Questions.

Does it replace Jira?

No. Jira stays where the work lives.

Are screenshots required?

No. They are optional.

Mac and Windows?

Yes.

What is MCP for?

Ask questions or build workflows on top of the same Bandanaut data.

Track Jira work. See what happened.

Real-time worklogs. Optional screenshots. Cost. MCP.

Start tracking time