[Feature Request] Rovo Agent Builder: Add "Get issue worklogs" read tool

jimmy.tu

[Feature Request] Rovo Agent Builder: Add "Get issue worklogs" read tool

Summary

The Rovo Agent Builder tool catalog currently includes Log work (write worklog), but is missing a Get issue worklogs (read worklog) tool. This makes it impossible to build custom Agents that can query worklog details — such as time spent, author, date, and description per entry — which is a fundamental need for teams that rely on Jira native time tracking.

Problem

Our team is trying to build a custom Rovo Agent that helps team members quickly check their daily/weekly time logging status — for example:

• "How many hours did I log today?"
• "Show me this week's worklog breakdown by task"
• "Did I log 8 hours every day this week?"

What we can do today:

• JQL with worklogAuthor and worklogDate can find which issues have worklogs — ✅ this works via the "Search with JQL" tool
• The "Log work" tool can write new worklogs — ✅ available in the tool catalog

What we cannot do:

• Read the actual worklog entries on an issue (author, timeSpent, started date, comment) — ❌ no tool available

This means the Agent can tell you "you logged work on PROJ-123 today" but cannot tell you how many hours or what you wrote in the description. That's like having a timesheet system where you can submit hours but can't review them.

The irony

Rovo Chat itself (the built-in assistant) does have access to getIssueWorklogs internally and can read worklog details perfectly. But when we try to build a custom Agent to provide the same capability with a better UX and guided prompts for our team, the tool simply isn't available in the Agent Builder catalog.

The Jira REST API GET /rest/api/3/issue/{issueIdOrKey}/worklog has existed for years. This is not a new or exotic endpoint — it's a core Jira API.

Expected behavior

Add a "Get issue worklogs" tool to the Rovo Agent Builder tool catalog with the following capabilities:

• Input: Issue key or ID, optional time range filters (startedAfter, startedBefore), pagination (startAt, maxResults)
• Output: List of worklog entries, each containing:
  • author (accountId, displayName)
  • started (date/time the work was performed)
  • timeSpent / timeSpentSeconds
  • comment (work description)
  • created / updated timestamps

Use cases this would unlock

1. Personal timesheet review — "Show my worklogs for this week, grouped by day"
2. Team time tracking — "How many hours did the team log on Project X this month?"
3. Compliance / audit — "Are all team members logging at least 8 hours on workdays?"
4. Project cost tracking — "Total hours logged against Epic ABC across all tasks"
5. Worklog reporting — Build Agents that generate weekly time reports automatically

Environment

• Jira Cloud
• Rovo Agent Builder
• Affects all customers using Jira native time tracking (non-Tempo)

Priority justification

Time tracking is one of the most common Jira workflows. The read-side tool (Get issue worklogs) is arguably more important than the write-side tool (Log work) that's already available, because every team member needs to review their logged time regularly, while logging can be done directly in Jira.

Thank you for considering this request. Happy to provide more details or examples if needed.

Nick [CodeCove]

@jimmy.tu, you can do this today with Timesheets for Jira, a free app that reads native Jira worklogs. Full disclosure, I work on it.

In Rovo Studio

The app adds its tools to Rovo Studio:

1. Edit your agent and open Tools.
2. Pick Timesheets and add Get My Timesheet.

It returns the current user’s hours per day for this week or last week, plus the working days with nothing logged. So “How many hours did I log today?” and “Did I log 8 hours every day this week?” are answered straight from it. The only setup on the people side: each person needs to be in a team in the app.

From Claude or Cursor

The same tools work over MCP. This part is early access from Atlassian for now.

1. A site admin goes to Atlassian Administration > Connected apps > Timesheets and clicks Enable tools.
2. Add this as a remote MCP server and sign in:
   https://mcp.atlassian.com/forge/879667b0-a01c-4427-a177-e923b24dc675
3. In Claude Code that’s one command:
   claude mcp add --transport http timesheets https://mcp.atlassian.com/forge/879667b0-a01c-4427-a177-e923b24dc675