Moving from Worklogs Report
Rebuilding a time-tracking report in RollGrid, and the two places the numbers will differ.
A worklog report answers "who logged what, when". In RollGrid that is a Timesheet tab, and most existing reports rebuild in a couple of minutes.
What maps to what
| In a worklog report | In RollGrid |
|---|---|
| The filter or project it covers | The report's source |
| Date range | The Timesheet tab's range — fixed dates, or a moving one like "last week" |
| Group by user | Group by Person |
| Group by team | Group by Team, using the team map in admin settings |
| Daily / weekly / monthly columns | Columns: day, week or month |
| Worklog comments | The "show worklog comments" switch |
| Minimum-hours highlighting | "Flag people under N hours" |
The quickest way
Start from the Weekly time by person template, point it at your filter, and change the range and grouping. That is most worklog reports.
Two places the numbers will differ
1. Permissions
RollGrid reads as you. If the old report ran with wider access, its totals were wider. A timesheet that looks short is usually this — check whether the work items whose time is missing are ones you can open in Jira at all.
2. Which day a worklog lands on
A worklog started at 11pm belongs to a different date depending on the time zone used to decide. RollGrid splits a worklog at midnight in its author's time zone where that is known, falling back to the site time zone in admin settings. An app that uses one zone for everybody will disagree with this at the edges of a day — if a weekly total matches but the daily split is a few hours out, this is why.
Two things that get better
- Leave and holidays are taken off before anyone is flagged for a short week, so somebody who was off is not reported as underworked.
- The same report can carry other tabs. A timesheet beside a roll-up of the same work items, read once, is a thing a dedicated worklog app cannot do.
A timesheet makes the report read worklogs, which costs more than reading work items alone. If a report is slow, a narrower source or a shorter range is the fix. See caching and limits.