Using itLogging time from an agent

Logging time from an agent

Most of the day’s work already gets described to an agent — the one you plan with, code with, or ask about a ticket. Calibro Track ships its own Rovo agent for exactly that, so recording the time is a sentence rather than a form: log the time we spent on IS-42, and it’s on your timesheet. Nothing watches your activity or guesses what you did. You say what you did, and the app writes it down.

Where it works today

Inside Jira, three ways in, and all come with the app — there is nothing to install or enable beyond Rovo itself. Outside Jira, the same tools are in Claude and Claude Code.

Use the Calibro Track agent, not the default one

Rovo’s default agent cannot see your timesheet. Anything to do with Calibro Track — logging, editing, submitting, starting or stopping a timer, asking what you have logged — goes through the Calibro Track Agent, which ships with the app. The Ask Track button at the top of the app opens it directly. Ask the default agent to log time and it will either say it can’t, or write to Jira’s own work log, which Calibro Track does not read.

The Ask Track button: Beside Help at the top of the app, ✦ Ask Track opens Rovo chat already on the Calibro Track Agent. One click, no searching. From then on the conversation is with our agent: it knows how to log, list, edit, submit and time your work, and it asks before it writes anything. This is the way in; the switcher below is the fallback.
Rovo chat in Jira: From anywhere else in Jira, open Ask Rovo, use the agent switcher at the top of the panel (it reads Rovo with a small arrow), search for Calibro Track Agent and pick it. Rovo remembers the choice for that conversation; a new conversation starts on the default agent again.
Your own Rovo agents: In Rovo Studio, edit an agent, open Tools → Add tools and filter by app: Calibro Track’s tools are listed under Connected apps. A team can build a “log my time” agent with its own instructions and nothing else in it.

In Claude and Claude Code

Calibro Track is listed in Claude’s connector directory. The same seventeen tools, run as you, against the same timesheet — so the session in which you fixed the bug is the one that logs the time: log the time we spent on IS-42.

Once per Jira site, an admin allows it. In Atlassian Administration, open Settings → Connected apps and turn on Allow external MCP access. Until then Claude can sign in but sees no tools. It is a site setting, not ours; Rovo is unaffected either way.
Add the connector. Open Calibro Track in Claude’s directory and choose Connect — or, in Claude, open Settings → Connectors and browse for it. On a Team or Enterprise plan, an owner may need to add it for the organization first.
Sign in and pick the site. Atlassian asks which site to connect. Choose the one Calibro Track is installed on, and accept.
Ask. What have I logged this week? is a safe first question: it only reads.

Claude Code signed in with the same Claude account picks the connector up with nothing more to do, and so does Claude Desktop.

Two differences from Rovo. There is no review card: Claude asks your permission before calling a tool, unless you have told it to always allow that one — worth keeping for Delete, Discard and the approval tools. And the Calibro Track Agent’s own instructions do not travel with the tools: Claude works from the tool descriptions alone, which carry the essentials — leave the date to the app, confirm before deleting or deciding — but if an entry’s issue or minutes look like a guess, say so before you confirm.

Not yet listed: ChatGPT, Codex and Cursor

The tools are served from one Atlassian address for every client, and other directories need things Atlassian’s address cannot yet provide — OpenAI’s asks the publisher to prove they own the server’s domain, which only Atlassian can do for its own address. It is on the roadmap.

What to 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 the entry 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.

Before a write, Rovo shows a review card with exactly what will be sent — issue, minutes, description, date — and waits for Confirm. The Calibro Track agent is also told to confirm the issue and the minutes with you when either is unclear, to look an issue up rather than guess a key, and never to invent a duration: if you didn’t say how long, it asks.

Leave the date to the app

Unless you name a day, no date is sent and the app fills in today in your own Jira timezone. That is deliberate: an agent has no clock of yours to read, and the first one we tested logged an evening’s work onto tomorrow because its own clock had already passed midnight.

What it writes

A draft entry on your own timesheet — the same row a typed entry makes, with the same rules. If your team requires a note, an entry without one is refused and the agent asks you for it. It shows up in My timesheet and on the issue’s Time tracking panel the moment it is written — a calendar open beside the chat redraws without a refresh — and it reaches an approver only when you submit it, exactly as before. The agent reports the entry’s ID, so a correction is one more sentence.

Nothing is written to Jira’s own work log. Calibro Track’s time lives in Calibro Track, whichever way it was entered.

The seventeen tools

What the agent can call, in the words it sees them by. Every one runs as you: against your own time, and, if you are an approver, against the time submitted to you.

Log time: Minutes on an issue, or a start and end time, with an optional note and date. Creates a draft; a time range lands it on the calendar grid.
List my time: Your entries between two dates, with totals per day and per status. How the agent finds an entry ID.
Time on an issue: Your entries and total on one issue, everyone’s total, and the original estimate.
Update, Delete: Change or remove one of your entries, including moving it to a different time of day. Draft and rejected entries only, like the timesheet itself.
Submit for approval: Send draft entries to the project’s approver. Entries still flagged for a note or a duration check are refused, and the error says which.
Find issues: Issues assigned to you, ones you logged on recently, and matches for a search — how the login bug becomes a key.
Timer status, Start, Stop, Discard: The same timer as Timing your work: one at a time, stopping writes the draft, under a minute pauses and asks.
Run a report: Totals grouped by up to three things — project, person, status, date, issue, or any Jira field by name — over a named period or two dates, as minutes, entries or utilization. Counts only time from projects you can see in Jira, like the Reports tab.
List reports, Run a saved report: The reports you can see, and any one of them run by name, with a named period resolved to now.
Time awaiting my approval: What is submitted to you, per person, with the entry IDs to act on. Empty, and says so, if you approve nothing.
Approve time, Reject time: Decide submitted entries for the projects you approve. A rejection needs a reason the submitter will read. Entries outside your projects are skipped.

What an agent cannot do

The tools are scoped to the person talking. An agent can only read and write your time, never a colleague’s, and it can only decide time that the Approvals tab would let you decide. Team rules apply unchanged: notes required, future dates allowed or not, the timer’s warning and cap. 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.

For approvers

If you approve time for a project, the same agent handles the queue. What is waiting on me? returns it per person with totals; approve Alice’s week confirms the person and the total, then decides; reject Bob’s Tuesday, wrong issue sends the reason along, and the agent will ask for one if you did not give it. Every decision shows Rovo’s review card first, and it lands in the same audit trail as a click on the page, under your name. The agent is told never to decide time you did not ask it to decide.

For admins

In Rovo 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. If Rovo is not enabled on your site, none of it appears there and nothing else changes.

Claude is the one switch, and it is Atlassian’s: Allow external MCP access under Settings → Connected apps in Atlassian Administration. Off, which is the default, no client outside Atlassian can reach the tools. On, each person still signs in as themselves and gets exactly what the page would give them — the same permissions and the same team rules.