I am admin in Jira. How to track hours logged in by all users and get the summary of it?

[tapan]

Hi,

I am admin in Jira. How to track hours logged in by all users and get the summary of it?

[Trudy Claspill · Accepted solution]

Hello @tapan 

Welcome to the Atlassian community.

Are the users using the native Log Work/Time Tracking feature to log their hours against work items?

Create and save a filter with this JQL:

timespent > 0

That will retrieve all items that have time logged against them.

In a dashboard add the Workload Pie Chart gadget. This is a native gadget.

• For the Project or Saved Filter field select the filter you created and saved previously
• For Statistic Type select whatever fields you prefer for grouping the data; i.e. Assignee, Priority, Issue type
• For Time field to report on select Time Spent

Save the gadget configuration. That will give you a display like this. Notice the grand total is shown below the chart.

[tapan]

Thanks a lot. It worked.

[Trudy Claspill]

You're welcome 

Since your question was answered and you were able to solve your problem, please consider clicking the Accept Answer button to mark your Question as Solved.

[Rahul_RVS]

Hi @tapan 

If you would be interested in detailed time tracking report for users, I can suggest our app

Worklogs Time Tracking in Jira & Timesheets

With this add-on, you can easily -

• Prepare your reports based on Project/Sprint/Issue Type/Assignees/Authors and various other filters
• Create user wise time reports in real time by grouping & categorizing data with aggregation
• Group your data to build more meaningful reports
• Enter Time Spent for multiple issues from Time sheet screen. With Calendar view and Board view
• CSV Export
• Dashboard gadget
• Add and use custom attributes to worklogs (like organization, billable status, work type, cost center, etc.) and create reports based on those attributes.

Disclaimer : I am part of the dev team

[Sarah Hempel_Tempo_]

Hi @tapan!

The second answer here covers the native options thoroughly — the JQL/Automation route works for a basic summary but hits walls pretty quickly when you need actual per-user, per-day breakdowns rather than just aggregate time-on-issue.

For an admin-level view of all users' logged hours, Tempo Time Tracker has a Pivot by User report built specifically for this: rows are issues, columns are team members, and you can switch between daily/weekly/monthly view. It also has a Timesheet report where you can select all users and set any date range — so you get a full picture of who logged what across all projects, without any manual aggregation.

Don't hesitate to drop another question here if I can help you further!

Disclosure: I work for the team behind Tempo Timesheets.

[Fatma Uzundemir from The Starware]

Hi @tapan

What you can do in native Jira:

1. Time Tracking Report (Project > Reports menu) — shows estimated vs. actual time per work item, scoped to a single project.
2. JQL filtering — using worklogAuthor and worklogDate, you can filter by a specific user/date range and see the "Time Spent" column, but you'll need to total it up manually.

That said, a ready-made, grouped summary of logged hours across all users simply isn't available in native Jira. If you're open to third-party apps, WorklogPRO Cloud covers exactly this gap. With WorklogPRO, here's how to see logged hours for all users:

• 📂 Open a Project Timesheet from the WorklogPRO menu (or build a Custom Timesheet based on a JQL/Filter that spans all projects).
• 👤 Check "Group by: Work Log Author (User)" in the view settings — each user's logged hours will appear row by row.
• 📅 Set the time range to Weekly / Monthly / Custom / Timesheet Period to get a summary for whichever period you need.
• 🧩 For a more detailed breakdown, switch to the Work Log Report or Pivot Report view and group by multiple criteria, such as user + project.
• 📤 Export the resulting table via Export to Excel or print it directly.

[Anastasia Andriyanova _Teamlead_]

Hi @tapan,

Glad to hear Trudy’s native workaround with the Workload Pie Chart worked for you! It’s definitely a solid quick fix if you just need a rough overview.

However, as Trudy and Hamza rightly pointed out below, there is a technical catch with native Jira gadgets: they group time by Assignee, not by the Worklog Author (the person who actually logged the hours).

In practice, if developer A and developer B both log time under a ticket that is currently assigned to developer C, the native chart will attribute 100% of those hours to developer C. This completely breaks the accuracy of a per-user summary.

If you ever need an exact breakdown without manual JQL or Excel gymnastics, you might want to look into TeamTime for Jira.

It’s a lightweight timesheet tool built on Atlassian Forge that groups logged hours cleanly by users, authors, and dates into simple tables. It does exactly what you originally asked for: tracks hours logged by all users and gives you a clean summary.

Plus, if your team has under 10 users, it’s completely free on the Marketplace.

Hope this helps!

Cheers,

Anastasia

(Full disclosure: I am part of the Teamlead team, the developers behind TeamTime)

[Agata Leśnowolska_SolDevelo]

Hi @tapan

If you are open to trying a third-party marketplace app, as a part of the Worklogs - Time Tracking, Time Reports, Timesheets team, I'd recommend our app as a price-competitive solution for time tracking and reporting where you can track hours logged by all users and get a summary of it.

With Worklogs, you can easily build time-spent-per-user reports in just a few clicks. Here are 4 of the most popular configurations our clients use:

1. Total time per user across all projects

2. Time per user broken down by project

3. Time per user broken down by issue

4. Project-first view with per-user breakdown

These are just the most common setups - you can create many different report configurations using up to 3 levels of grouping with all your Jira native and custom fields (e.g., Priority, Sprint, Component, Label, Fix Version, Epic, and more). This means you can tailor reports to match exactly how your organization tracks and reviews time.

All of these reports can also be:

• Viewed as a pie or bar chart for a quick visual summary of time distribution across users

• Displayed on a Jira dashboard using the Worklogs dashboard gadget, so leadership can check in anytime without opening the app

• Exported to Excel for further analysis, payroll, or invoicing
• Shared via URL with stakeholders who need visibility

If you'd like to see this in action, you can book a demo session with us, check out the app's documentation, or test it with a 30-day free trial.

Feel free to reach out if you have any questions!

[Anton from JetHeads_io]

Hi @tapan! 👋

The Workload Pie Chart gadget Trudy pointed you to is a solid quick win — it'll give you that grand total of time spent grouped by assignee right on a dashboard. Where it stops is detail: it's a single snapshot pie, so there's no real date range, no per-user table you can read row by row, and nothing to export and hand to someone.

So if you find yourself needing more than the one number, JetTime (a third-party Jira app) does the same "hours by all users" view but as a full report you can break down and share.

• Hours per user as a table, not just a pie — across every project
• Any date range (this/last week, month, quarter…), so you can compare periods
• Drill further — group or filter by project, account, or custom field
• Export to PDF, Excel, or CSV for management
• Runs on Atlassian — your worklog data stays inside Atlassian Cloud, we don't have access to it

👉 JetTime on the Atlassian Marketplace

— Anton, JetTime founder

[Hamza Chundrigar]

Hi @tapan 

If you mean the hours breakdown your team logs on work items, nothing built into Jira as a native OOTB functionality produces a per-user hours summary, on Free or any other plan.

On Free, the practical no-cost option is JQL plus CSV export or Jira Automation. But if/when when you need totals split by user and date then you'd need to use the REST API or a Marketplace time tracking app.

You can use Jira Automation to send a scheduled email report, but it works best as a lightweight summary of work items with logged time. Again, it won’t be a full timesheet grouped by each user’s individual worklog entries. If that suffices then you could

1. Go to Project settings, then Automation.
2. Select Create rule.
3. Choose the Scheduled trigger.
4. Set the rule to run daily or weekly.
5. Add Lookup work items.
6. Use JQL like this, changing the project key and dates as needed:

   • project = ABC AND worklogDate >= startOfWeek() AND worklogDate <= endOfWeek()

7. Add Send customized email.
8. In the email body, add something like:

   • Work items with logged time this week:
     
     {{#lookupIssues}}
     * {{key}} - {{summary}}
     Assignee: {{assignee.displayName}}
     Total time on work item: {{timetracking.timespent}}
     {{/}}

If you mean all Jira projects, create the rule from Settings, then System, then Global automation instead, and use a wider JQL query such as:

worklogDate >= startOfWeek() AND worklogDate <= endOfWeek() ORDER BY project, updated DESC

One important limitation to keep in mind is that worklogDate finds work items where someone logged work during the period. The Time spent value is the aggregate time on that work item, not just this week’s time and not split by each person. 

On the Free plan, keep the automation small. Jira Free has 100 automation flow runs per month, Send customized email is limited to 100 emails in 24 hours on Free and trial sites, and Lookup work items only uses the first 100 matching work items.

For an exact all-users summary, the better native technical route is the Jira REST API: get worklog IDs from /rest/api/3/worklog/updated, then fetch the rows with /rest/api/3/worklog/list and group them by author, started date, and timeSpentSeconds. If you don’t want to maintain that, then perhaps look into a Marketplace time tracking app and use it as the reporting layer.

If you have under 10 users, the Atlassian Marketplace might have free apps worth evaluating at that tier that could likely address what you're looking for.

Cheers

[Trudy Claspill]

I concur with the statement. In my answer I selected Assignee for the grouping so the time is grouped based on the current Assignees in the collected issues, not by the person that actually logged the time.

If the author wants total time per each user that logged the time, that will require a third party app from the Marketplace or a custom solution that leverages the REST API.