Every Jira admin has fielded the same question: "How much time did the team spend on Project X last month?" It sounds simple. Then you open the native worklog UI, realise it answers per-issue but not per-person, per-project, or per-category — and reach for a spreadsheet. One of the most-viewed worklog questions on the Atlassian Community was first asked in 2012, and it still gets thousands of views every month. The pain has not gone away.
Time tracking in Jira Cloud should not be this hard. This article walks through how Worklog Reports for Jira — a free Forge app from VIEW26 — turns the worklogs your team is already creating into instant timesheets, billing exports, and capacity views, without JQL gymnastics or a paid timesheet platform.
When teams ask for help with time tracking on Community, the same handful of frustrations come up again and again:
Per-person reporting is painful. Native Jira lists time per issue, not per assignee, project, or category.
Capacity dashboards don't exist out of the box. Managers want a graphical view of "where did this team's hours go?" — and there isn't one.
Monthly client billing is a copy-paste exercise. Exporting clean, invoice-ready hours per project per user usually means writing JQL, then massaging CSVs in Excel.
Meetings vanish from worklogs. Hours spent in meetings rarely get logged, so the timesheet is wrong before it leaves the door.
Finding issues with no worklogs is hard. A common Community question — and JQL alone doesn't reliably solve it.
Each of these is a small problem on its own. Together they push teams toward heavyweight third-party suites that cost more than they need to.
Worklog Reports is a free, Forge-built app for Jira Cloud. Because it runs on Atlassian's infrastructure, your worklog data never leaves the Atlassian ecosystem — there's no external server to provision, no security review marathon, and no per-user fee. Install it from the Marketplace, hand out permissions, and your team is logging structured time within minutes.
Here's what it does for the five pain points above.
Logging work should take seconds, not a context switch. Worklog Reports gives the team four ways to enter time — Calendar, List, Dashboard, and Timesheet views — so people can log the way they already think. Click any slot in the weekly grid (or the + Log button on a date), pick the issue with smart search, choose a category (Development, Design, Testing, Meeting, and any custom ones your admin defines), and save. The form pre-fills date and time so a typical entry takes under ten seconds.
The reporting engine is built around how stakeholders actually phrase questions. Filter by date range (day, week, month, or custom), pick projects, pick assignees, then aggregate by user, project, category, or issue type — or chain them ("by project, then by user"). Common scenarios are pre-modelled: a Weekly Team Report aggregates the last seven days by category; a Monthly Client Billing report scopes a single project to "Last Month" with a detailed list aggregation.
When the report on screen is the report you want to send, click Export to PDF for stakeholder reviews or Export to Excel for accounting. Columns are clean, totals are computed, and the file is ready to attach to an invoice or drop into a board pack.
This is the differentiator. Connect a Google Calendar once, and your meetings render as blue cards directly inside the Calendar view, next to your worklogs. Two things happen as a result:
Conflict detection on the Log Work form. When the date, start time, or duration of a worklog overlaps an existing calendar event, the form warns you before you save — no more double-booking your own timesheet.
Create Jira-linked meetings without leaving the app. Add a meeting (or a sick-leave / holiday block), invite Jira users by name or external attendees by email, and the event lands on Google Calendar with the right participants attached.
Ajay _view26_
0 comments