Rovo time tracking for Jira: log, submit and approve time by saying it

Most of the day’s work already gets described to an agent. Calibro Track ships its own Rovo agent so that recording the time is a sentence rather than a form: log the time we spent on IS-42, and it is on your timesheet. Nothing watches your activity or guesses what you did.

Written 2026-09-09 from the app’s own documentation. Everything here is shipped, not planned.

What it is

Rovo is Atlassian’s AI layer for Jira and Confluence, and a Forge app can give it tools. Calibro Track declares seventeen and ships an agent, the Calibro Track Agent, that knows how to use them. It comes with the app, on every plan, at the same price. If Rovo is enabled on your site there is nothing to install or configure; if it is not, none of this appears and nothing else changes.

Three ways in:

The Ask Track button

Beside Help at the top of the app. One click opens Rovo chat already on the Calibro Track Agent.

Ask Rovo, anywhere in Jira

Open the agent switcher at the top of the Rovo panel and pick Calibro Track Agent. Rovo’s default agent cannot see your timesheet; ask it to log time and it will either decline or write to Jira’s own work log, which Track does not read.

Your own agents

In Rovo Studio, add Calibro Track’s tools from Connected apps to an agent of your own, with your own instructions around them.

What you can say

Plain sentences. The agent reads the tool descriptions and works out the rest.

• Log 45 minutes on IS-42 for today: pairing on the migration runner.
• Log 2 to 3pm on IS-42 as the design review. — a time of day places it on the calendar, and the minutes follow.
• What have I logged this week?
• Start a timer on IS-42. … and later, stop my timer.
• Change entry 60003 to 30 minutes.
• Submit my week.
• How much time went to each project this month? — a report, grouped by what you named, over the period you named.
• Run my “Time by client” report.
• What is waiting on me? … approve Alice’s week. — for approvers.

The rules it keeps

1. It confirms before it writes. Rovo shows a review card with exactly what will be sent — issue, minutes, note, date — and waits for Confirm. The agent is told to confirm the issue and the minutes with you when either is unclear, and to look an issue up rather than guess a key.
2. It never invents a duration. If you did not say how long, it asks.
3. The date is the app’s, not the agent’s. Unless you name a day, no date is sent and the app fills in today in your own Jira timezone. The first agent tested logged an evening’s work onto tomorrow because its own clock had passed midnight; this rule is why that cannot happen now.
4. It writes to Calibro Track, not to Jira’s work log. The entry is an ordinary draft on your timesheet, with the same rules as a typed one — if your team requires a note, an entry without one is refused and the agent asks for it.
5. Everything redraws. A calendar open beside the chat, the issue panel, another tab: all of them show the entry the moment it exists, with no refresh and no polling.
6. It is scoped to you. The agent can only read and write your own time, and can only decide time the Approvals tab would let you decide. Team rules apply unchanged. A site whose subscription has lapsed refuses every write from an agent the way it refuses them from the page, and still answers every read.

The seventeen tools

What the agent can call, in the words it sees them by. Every one runs as you, and every one is the same operation the page performs.

Why it doesn’t watch you

Most “automatic” time tracking works by observation: read the calendar, the commits, the editor, the issue activity, and propose entries for the person to accept. Calibro Track does something different on purpose. It hands its own actions to the agent you are already talking to, so the record is what you said rather than what software inferred. No inference, no suggestions to review, nothing running in the background, and nothing about your activity leaving your Jira site — the app declares no network egress at all. The cost is that you have to say it; the benefit is that a timesheet built from your words is one you can stand behind in an approval.

For admins

There is no switch. The agent and the tools arrive with the app and follow the permissions already in place: whatever a person can see in Jira, they can log against, and whatever they can do on their timesheet, an agent can do for them. Nothing reaches Jira’s own work log. Rovo must be enabled on the site; Atlassian’s own terms for Rovo apply to the chat itself.

Not yet: Claude Code, Cursor, Codex

The tools are written so that any MCP client could call them, and Atlassian’s public RFC describes each installation getting an endpoint for exactly that. Atlassian has not opened app tools to clients outside Rovo yet. When it does, the same seventeen tools appear there with nothing to change on our side; it is on the roadmap. Until then, an agent in your terminal can reach Jira’s own work log through Atlassian’s MCP server, but not Calibro Track.