What the native report actually shows
Jira Software's built-in Time Tracking report lives under a single project's Reports section and lists that project's issues with their original estimate, remaining estimate, and time logged. It's an estimate-vs-actual view for one project's backlog, scoped to whatever board it's attached to. Team-managed projects often don't expose it at all, since it's a classic-project reporting gadget.
Why it stops at one project
The report is built around a project's board and its issues, not around a person or a time period. It has no concept of "everything this person logged this week," because that would mean pulling worklogs from every project they touch and grouping by person instead of by issue. That's a different shape of report entirely, and it's the reason a whole category of Jira marketplace apps exists specifically to add cross-project, per-person timesheet views.
What a cross-project view actually needs
- Worklogs pulled across every project the person (or team) works in, not one project at a time.
- Grouping by person and by day or week, not by issue.
- Project subtotals, so a manager can still see which project the hours belonged to even though the report spans several.
- A date range that isn't tied to a sprint or board, since a billing period or a payroll week rarely lines up with either.
Working around it manually
Without a dedicated report, the manual version is opening each project's issues in turn, filtering worklogs by person and date by hand, and adding the numbers up in a spreadsheet. It works for one person checking one week. It stops working the moment you need it for a team across a month, since the manual effort scales with people times projects times weeks.
Where the workaround stops making sense
Once you're doing this manually for more than one or two people, see how to build a Jira timesheet report by user and project, or, if you also need approvals and billing rates rather than just a report, a Tempo Timesheets alternative for exporting Jira worklogs for how the two categories of tool differ.
One export, every project the person worked in
Worklog Export for Jira pulls worklogs across the projects and users you choose for a chosen date range, and builds a pivoted summary by person and day or week with per-project subtotals, plus a full detail sheet, generated in your browser with no data leaving Jira. It's built by Cody Labs and is not affiliated with Atlassian.
See Worklog Export for Jira