Someone asks for last month's hours by person. You open Jira, and there's nowhere to click.
Jira time tracking is fine at the work item level — estimated time, time spent, remaining. What it doesn't do is turn that into a timesheet: people down one side, days across the top, totals everywhere. That's what finance asks for, what client billing runs on, and what Jira doesn't have.
TL;DR
- Worklogs are the unit of time tracking in Jira, and they do their job.
- There's no native timesheet view, no aggregation across projects, no export of work logs.
- JQL finds work items touched in a period, not totals per person.
- Timesheet reports, billable hours tracking, and timesheet approvals all need an app.
How Jira time tracking actually works
Time tracking is always enabled in Jira Cloud, on every plan including Free. To track time spent on something, open the work item, select ••• then Log work (or click the Time tracking field), enter the hours and optionally a description. Just a few clicks, and manual entry becomes a Jira worklog: who, how long, against which item, on what date.
Three things decide whether your team can do it at all:
- Permissions. Users need Work on work items in that space's permission scheme. Editing and deleting work logs are separate permissions again — Edit own, Edit all, Delete own, Delete all. Anyone with Browse project can see the time data.
- Field visibility. The Time tracking field has to be visible on the screen. If people say there's nowhere to log time, this is usually why.
- The provider. Admins can point Jira to a different time tracker from the Atlassian Marketplace instead of the built-in one.
One more setting people miss, and it's a privacy and security question as much as a reporting one: you can restrict who sees whose work logs by role or group. Leave it off, and logged hours are visible to anyone with access to the Jira issue, which matters if you're logging time against client work.
Why there's no timesheet in Jira
A timesheet answers "who spent how long, when". Jira's data model answers "how much time is on this work item". The gap shows up fast.
- Reports are work-item-first and project-bound. The Time Tracking Report sits inside a single project and lists items with estimated time against actual time. The User Workload Report handles one person at a time. Neither aggregates across your Jira instance, which is where most project managers stop — there's nothing resembling advanced reporting on your team's time in native Jira, on Cloud or Jira Server. This is also where tracking progress gets awkward. You can see how one work item is doing against its estimate, but not how a person's week is filling up, or whether delivery teams are on course for the month.
- JQL finds items, not hours. worklogAuthor = "jane" AND worklogDate >= startOfMonth() returns every Jira issue Jane logged against. Not her total, not a day-by-day view. Export those items, and you get all time ever logged on them, not just the hours inside your window.
- No export of work logs. You can export work items from a Jira dashboard or filter. The individual worklogs behind them don't come along.
- No money, no approvals. Jira doesn't connect time data to rates, cost centers, or project cost. There's no billable versus non-billable flag, no custom worklog attributes to tag a cost center or client against an entry, and no approval process — no concept of submitted timesheets waiting on a manager, and nothing in the Jira workflow that marks an entry as final.
So: Jira is a reasonable place to log time and a poor place to read it back.
How to do Jira timesheet tracking natively (3 ways)
The easiest way would be adding an app. If you'd rather not add an app, there are some workarounds you can try:
- Build a Jira dashboard. The Time Tracking Report gadget, plus filtering results using worklogDate and worklogAuthor gives you a rough picture of who touched what. Pie charts by assignee help for a basic read, though they count items rather than hours. If the team already starts their day on a dashboard, putting a logging gadget there removes the main excuse.
- Save a filter per person. Workable at five people, painful at fifty.
- Pull work logs through the REST API. GET /rest/api/3/issue/{key}/worklog, paginated, then build the grid yourself. Teams doing client billing often end up with a script running this weekly for further analysis in a spreadsheet, with custom fields mapped to whatever their finance system needs.
What a Jira timesheet plugin adds
I work on one of these apps, so weigh the rest accordingly. There are plenty on the Atlassian Marketplace, and they differ mostly in what they add on top of worklogs.
Planyway (an app that combines time tracking, including timesheets, capacity, roadmaps, and a ton of other features) takes the friction out of the part that actually breaks: getting people to log. Among the core highlights of the apps is that hours go in from wherever someone happens to be, and the timesheets fill themselves from there.
- Every hour lands in Jira — reports fill themselves. Entries go straight into Jira worklogs (🔥). Nothing to duplicate, nothing to sync, nothing to assemble by hand at the end of the month. That's also why logging is easy in the first place: there's no second tool in the way.
- The team logs the way they already know. Timer or manual entry inside the Jira issue, a list of the day's entries, a calendar you drag work onto, or a personal timesheet where you type hours into a cell. Same habits as Tempo, Toggl or Clockify, now inside Jira — which takes the "please fill in your timesheet" conversation off your plate.
➡️ Try time tracking with Planyway
- You can then slice it for whatever you need to answer: time by project or epic, planned vs tracked, and, of course, timesheets.
➡️ Try timesheets in Planyway.
- And capacity sits next to the hours. The same Jira issues appear on a timeline with each person's real availability, so you can see who's booked past their hours next week, not only who logged what last week.
Best practices for time tracking in Jira
Tooling is the easy half. Time management in a team comes down to three decisions, and none of them is a purchase.
Decide when people log. At the switch, not at the end of the day. End-of-day logging is where guessing and rounding start, and rounded hours are how budgets drift from reality without anyone noticing. Logging as you move between tasks takes ten seconds and doesn't rely on memory.
Decide where logging lives. It gets reliable when it's part of the workflow rather than a separate chore — a field in the work item people already have open, a timer one click away, an intuitive interface they don't have to think about. If logging means switching apps, it won't happen consistently, whatever you install.
Decide what you'll do with the data. Hours nobody reads are hours nobody logs. Pick the question first — what a project costs, whether estimates are drifting, who's overloaded — and build the one report that answers it. Then share it with the whole team, not just managers. Blank rows visible to everyone do more for compliance than reminders ever will.
Get those three right and even native Jira plus a spreadsheet will carry you further than most teams expect. Get them wrong and no Jira timesheet plugin will save the numbers.
