The timesheet view is built for grouping and for the details on every row. When you only want one fact, like the hours on a work item this week, you are still arranging that layout. Ask for the fact, and the answer comes back in a single reply.

Tempo Timesheets has a Rovo agent called the Timesheet Worklog Assistant. You tell it the work item, the hours, and the date in a sentence, and it prepares the entry.

Listing what you already logged

Ask for the period you care about:

What did I work on this week? List all my logged work items with spent hours and dates.

The reply gives the date, the Jira work item, and the time spent:

2026-10-05 → AP-103 → 4h
2026-10-06 → AP-440 → 4h

Other users’ hours stay out

Asking about other users does not widen that list. Try:

List all worklogs, including the date and time spent, and group them by author.

“All worklogs” still means your entries. The assistant returns only the current user’s worklogs. If you insist on other users’ worklogs, the answer is:

If you need to see a report grouped by multiple authors or projects, you can use the Tempo Reports feature.

View All Worklogs in Jira does not change this, and neither does the matching permission in Tempo. A view across authors or projects is a Tempo report, not a chat reply.

Adding a worklog

A complete sentence is enough for a draft:

Log 2 hours and 30 minutes on AP-440 for today with the description "Bug investigation and testing"

From that line it takes the key AP-440, the duration of 2 hours 30 minutes, the date today, and the description.

“Log work 3h for today” names no work item. The assistant finds the work item assigned to itself and uses that.

Either draft waits. It asks, “Shall I go ahead and log this?” Nothing is written to Jira until you answer, so you can confirm the assigned work item it found.

Custom attributes are skipped

Put the attribute names and values in the prompt and they still do not land on the worklog. The basic fields do: work item key, date, duration, and description. You finish the rest on the timesheet.

Log 2 hours on this work item for October 10, 2026. Set Work Type to Development, Billable to Yes, and Test Cases Executed to 10.

The assistant logged it and then explained the gap:

I have successfully logged your work.

Issue

AP-442

Day

2026-10-10

Start time

11:34:21

Time Spent in hours or minutes

2h

Description

Concurrent checkout requests cause inventory overselling and intermittent payment capture failures

The worklog was created successfully with the standard fields. However, since the system did not return an error requesting specific work attributes (like "Work Type", "Billable", or "Test Cases Executed"), I was unable to attach those custom values to this entry.

If you need to ensure these specific attributes are set, please update the entry manually here: View my timesheet

Work Type, Billable, and Test Cases Executed never reached AP-442. The standard worklog did, and the reply points you at the timesheet for anything further.

Two more limits

Logging for someone else. The same personal scope applies when you create an entry. Naming another author in the request does not make the assistant log time as that person.

An entry that is already saved. Adding a detail, or filling a custom attribute on a worklog that already exists, is not done in the chat. You get a link to View My Timesheet and make the change in Tempo.

Tempo Trackers

A tracker can start in the same conversation, for a work item you name or for the one in your current context. Ask what is running and you get active trackers and ones started earlier, each with its status, start time, and related work item. Stop one and the assistant can turn that elapsed time into a worklog, after the same confirmation it uses for an entry you typed.