Changelog

Log time from Claude and Claude Code

Calibro Track is now in Claude’s connector directory. The same seventeen tools the Calibro Track Agent uses in Rovo — log, list, edit, submit, time, approve, report — reach Claude, Claude Desktop and Claude Code, so the session where the work happened can be the one that records it: log the time we spent on IS-42. Every call runs as you, under your own Jira permissions, against the same timesheet, and lands as a draft exactly as a typed entry would. Nothing is watched and nothing leaves Atlassian’s platform except the answer to what you asked.

A site admin turns it on once, with Allow external MCP access in Atlassian Administration; after that each person adds the connector in Claude and signs in to their site. ChatGPT, Codex and Cursor are not listed yet — their directories need something from Atlassian’s side first, and they stay on the roadmap. Logging time from an agent has the setup.

Ask the agent for the numbers

The Calibro Track Agent now runs reports from the words you use. How much time went to each project this month? groups by project over this month and answers with the totals; time by person and status last month groups by two things; utilization by user this quarter reads the same numbers against each person’s weekly target. Any Jira field is a grouping, by its name — by assignee, by epic, by the Client field — the same claim the Reports tab makes, with no configuration. Ask for a grouping it does not know and it tells you what it does. Reports you have saved are there too: run my “Time by client” report runs it as of now. Three new tools, seventeen in all, and every run counts only the time from projects you can see in Jira, exactly as the page does.

The agent takes approvals

The Calibro Track Agent now does the Approvals tab’s work for the people who decide. What is waiting on me? answers per person, with totals and the entries behind them; approve Alice’s week confirms the person and the total, shows Rovo’s review card, and decides; reject Bob’s Tuesday, wrong issue sends the reason along, and the agent asks for one if you did not give it. Three new tools — Time awaiting my approval, Approve time, Reject time — and every one goes through the same rule as the page: an agent can decide exactly what you could decide on the Approvals tab, in your name, in the same audit trail, and nothing else. Fourteen tools in all; the docs have the approver’s page.

A Rovo agent that manages your time in plain language

Calibro Track now ships its own Rovo agent. Press Ask Track at the top of the app — or open Ask Rovo in Jira and switch to Calibro Track Agent — and manage your time by saying what you did: log the time we spent on IS-42, log 2 to 3pm on the design review, what have I logged this week, start a timer on this issue, submit my week. The agent is the way in — Rovo’s default agent does not carry these tools — and it knows the rules: confirm the issue and the minutes, never invent a duration, leave the date to the app unless you named a day. Behind it are eleven actions, every one the same thing the page does, scoped to the person talking and refused where the page would refuse. Log, list, edit, delete, submit, find issues, and the timer’s status, start, stop and discard. Rovo shows what it is about to send and waits for you to confirm; the app fills in today from your own Jira timezone rather than letting the agent guess; and nothing reaches Jira’s own work log. No activity is watched and no entry is proposed: you say what you did, and it is written down. And it is on your timesheet as the agent says so: every surface you have open — the calendar beside the chat, the issue panel, another tab — redraws the moment an entry is written anywhere, with no refresh and no polling behind it.

Teams that build their own agents in Rovo Studio can add the same tools under Connected apps and write their own instructions around them. Clients outside Rovo, such as Claude Code, Cursor and Codex, wait on Atlassian opening app tools to them — on the roadmap, and nothing changes here when it lands. Logging time from an agent has the details, including what an agent cannot do.

Time follows the issue

Jira moves issues between projects, renames project keys and deletes issues, and until now the time logged against them stayed exactly where it was written — under the old key, in the old project’s approval queue. Calibro Track now listens for those changes. When an issue moves, every entry on it takes the new key and, by default, follows it to the new project, so the right approver sees it and a report by project reads as if it had always been there. When a project’s key changes, every entry in it is renamed. When an issue is deleted, its time is kept and marked: the key stops being a link and every surface says Deleted issue instead of pointing you at a page that is gone. A timer running on a deleted issue stops itself into a flagged draft, so nothing that was captured is lost.

Two new switches in Settings → Team defaults decide what happens to time already logged. When an issue moves to another project chooses whether all of its time follows, or whether time already approved stays reported and paid under the project it was approved in. When an issue is deleted chooses whether unsubmitted time is kept and marked, or removed — anything an approver has seen is always kept. Jira usually tells the app within seconds; opening a timesheet or the issue itself catches anything that was missed. The Team defaults and Submitting and approvals pages describe both.

Five languages

Calibro Track now speaks German, Spanish, French and Portuguese (Brazil), alongside English. The whole interface is translated — timesheets, approvals, reports, settings and the payroll export — and so are the messages the server sends back, so a refused save explains itself in the same language as the button that was pressed. Even the module names Jira draws outside the app, like the issue panel’s title, follow along.

There is nothing to configure: each person sees the app in their own Atlassian language, two people on one site can read the same timesheet in two languages, and any language we don’t ship yet falls back to English. European Portuguese reads the Brazilian catalog before falling back. Your Jira data is untouched — this is the app’s own wording, never your issues, fields or worklogs. More languages follow where the votes point.

Payroll export

Approved hours, in the shape your payroll system already reads. An admin defines the file once in Settings → Payroll export — presets ship for ADP Workforce Now, Gusto, Paychex Flex, Workday, QuickBooks Payroll and Rippling, plus a generic CSV, and every column stays remappable — and whoever runs payroll exports it from the Approvals tab for any date range. Before anything downloads, the run screen shows the file’s totals, what changed since the last export of the same range, and everyone who is not in the file, by name, with the reason and the fix. Re-runs are first-class: late approvals and corrections land in a fresh file, down to a single person’s fixed week, and every entry carries the export it went into so the queue can say what was paid.

Rounding, a configurable payroll day boundary for night shifts, and an overtime split against each person’s weekly target are all part of the file definition — and every adjustment the export makes is reported on the run screen rather than absorbed. The docs have a new Payroll export page.

Plan time ahead

Logging time on a future date is now allowed by default — putting next week’s planned hours on the timesheet is a normal way to use one. Teams that prefer the stricter reading, where a date in the future is a slip of the picker, get it back with a new switch in Settings → Team defaults. If an admin has already saved team settings, their choice stands either way — the new default only decides for installs that never made one.

Also in this release: when a project has no approver, the red dot on the Settings tab now carries through to the Approvers group inside it, so the pane that needs opening is marked instead of hunted for.

The whole page is yours now

The app used to sit under a page heading Jira drew for it — a second “Calibro Track”, directly below the sidebar entry you had just clicked, spending a header’s worth of height to repeat it. That heading is gone. The app now owns its full page: its name and tabs share one slim row, and everything below it — the week, the calendar, the queue — gets the room the heading used to take.

A lighter timer

A small performance patch. The timer now checks in with the server only while its tab is actually on screen, and each check asks for less — a Jira tab left in the background costs nothing and still catches up the moment you come back to it. Nothing changes in how the timer looks or behaves.

The issue view, split in two

The issue panel is now for capturing time: the timer and composer, progress against the issue’s estimate, your own recent entries with their drafts submittable in place, and — for approvers — the queue. The full history moved to a new Time log tab in the issue’s Activity section, beside Jira’s own Work log: everyone’s time, the Everyone/Just me toggle, and inline editing on your own rows.

This release also makes the app comfortable on large Jira sites. The approver settings page and search projects server-side instead of fetching them all, long lists are capped and say so on screen, and every total is computed exactly however busy the issue or the queue behind it.

Calendar entry mode

A second way to fill in a week. Drag a block onto the calendar to log time at the hour it happened, drag its edge to change how long it took, or move it to another day. The list stays and the entries are the same entries — you pick whichever matches how you think about your week, and Settings decides which one your timesheet opens in.

First release

Timesheets, single-step approvals, and a report builder that groups by any Jira field including custom ones. Runs entirely on Forge.