Team timesheet

Last updated: 18 September 2026

The Team tab shows how much time people logged in Jira, day by day, over a period you choose. Pick the people, pick the period, and OnTask adds up their worklogs. Open a person's row to see which issues the time went on.

It reads only what Jira already lets you see, and it reads it as you. It keeps none of it.

Where it is

Open Apps → OnTask and choose Team in the tab bar at the top. Focus, the other tab, is the dashboard with your ranked work and the clock. Switching tabs does not affect a running clock.

The Team tab is there on every site that has OnTask, for everyone who uses OnTask. There is nothing to switch on.

What it shows

The grid has one row per person you picked and one column per day.

Time from Jira worklogs, however it was logged: through OnTask, in Jira itself or by another app. The people you pick do not need to use OnTask.
Every person you picked gets a row, in the order you added them, even if they logged nothing. If nobody logged time you can see in the period, the tab says so instead of showing an empty grid.
Each day column shows the day number and weekday. Weekends are tinted and today is marked. A cell shows time like 1h 30m, <1m for less than half a minute, or nothing.
A Total column for each person, and a totals row at the bottom. Every total is added up from the exact time logged, and each cell is rounded to the nearest minute on its own, so a total can differ from the sum of the cells next to it by a minute or so.
Open a person's row to see the issues they logged time on: the issue key, which links to the issue, and its summary. The issue with the most time comes first.

A long period scrolls sideways, and the names stay in view.

The grid shows issue keys, issue summaries and durations. It never shows the comment on a worklog.

Under the grid, a note is always shown. It reminds you that the figures come from worklogs you are allowed to see, names the timezone the days follow (your Jira timezone, or the fallback described under Why someone's time can look incomplete), and says that worklogs on issues you cannot open are not included.

While the grid loads, a progress line says how far it has got, for example Reading worklogs… 34 of 120 issues. If Jira asks OnTask to slow down, it waits and tries again a few times. If Jira keeps refusing, OnTask stops asking, shows what it has read so far and marks the grid Incomplete; if even the issue search cannot run, it says Jira is busy and offers to try again.

Choosing a period

Pick one of Today, This week, Last week, This month, Last month or Custom.

Weeks start on Monday.
This week and This month run to the end of the week or month. Days still to come are shown empty.
Custom gives you two dates, from and to. A custom period can be at most 93 days. If the dates do not work, the tab tells you why.

Choosing people

The first time you open the tab it shows just you, for this week.

Add people finds colleagues by name or email address. Type at least two characters and pick from the list. If you do not have Jira's Browse users and groups permission, Jira only finds someone by their exact full name or email address; the tab says so under the box, so an empty list does not look like the person does not exist.
Me is a shortcut for yourself.
Everyone you picked appears as a chip. Remove someone from their chip.
You can pick up to 50 people at a time.

Saved views

The Current sub-tab holds the selection you are working on. It is not saved.

Save view stores the current people and period under a name you give, such as "monthly" or "my team weekly". The view appears as its own sub-tab next to Current.

Only you see your saved views. Nobody else on the site can see, open or use them.
A view keeps the period as you chose it. A view saved on This week shows the current week each time you open it. A custom period keeps its dates.
Change the people or the period while a saved view is open, and Update view appears. Press it to save the change into that view.
Rename changes a view's name. Delete removes the view after you confirm.
The Team tab reopens where you left it: on the saved view you had open, or on Current if that is where you were, or if the view has since been deleted. Current always starts again as just you, this week.

The limits: a name can be up to 60 characters, and no two of your views can share a name, whatever the capitals. You can keep up to 20 views; to save another, delete one first.

A view can lose people without you doing anything. When a person deletes their OnTask data, or their Atlassian account is closed, they are removed from every saved view. A view left with nobody in it is deleted. A site administrator's Delete everyone's removes all saved views.

A saved view cannot quietly bring someone back. If a view changed while you had it open — because someone in it deleted their data, or because you changed it in another tab — Update view and Save view do not overwrite it. The tab reloads the view, keeps the period you had picked, leaves out anyone who is no longer in the view, and tells you to check it and try again. Renaming a view, or only changing its period, never changes the people in it.

Why someone's time can look incomplete

The grid shows what Jira lets you see. That is not always everything a person logged.

Issues you cannot open. Time logged on issues outside your Jira permissions is not included. If some issues turned up but could not be read, a notice tells you, and their time is not in the grid.
Worklog visibility. A worklog can be restricted to a group or a project role. If you are not in it, Jira does not show you that worklog, and neither does OnTask.
Your timezone, not theirs. The days follow the timezone in your own Jira profile. If Jira does not give OnTask a timezone your browser can use, the tab falls back to your browser's own timezone, or to UTC if that does not work either; the note under the grid always names the timezone it used. A colleague in another timezone may see the same worklog on a different day in their own Jira.
When the work started. A worklog counts on the day it started, not the day it was entered. Backdated time lands on the day it was backdated to. A worklog counts in full on its start day, even if it ran past midnight, and only if it started inside the period.
Very large selections. OnTask reads at most 1,500 issues for one grid. Past that it stops and marks the grid Incomplete. Pick fewer people or a shorter period.
Jira too busy. If Jira asked OnTask to slow down and kept refusing, OnTask stops rather than wait minutes, does not count what it could not read, and marks the grid Incomplete. Try again in a minute.
Something else went wrong. If an answer from Jira could not be read, or your Jira session ended while the grid was loading, the grid is marked Incomplete and the notice says which of these it was. For a session that ended, reload the page.
Someone Jira does not recognise. If Jira cannot resolve one of the people you picked — a closed account still in a saved view, for example — that person keeps an empty row, a notice says so, and the grid is marked Incomplete.
Time logged since the grid loaded. The grid reads Jira when it loads, so time logged afterwards shows up the next time it loads.

Whenever the grid is marked Incomplete, the notice above it lists the reasons that applied and offers Retry.

What is stored

Nothing about anyone's time. The grid is worked out in your browser each time it loads, then thrown away.
No names or avatars. The names and avatars on the grid, and in the people search, are read from Jira into your browser each time and not kept.
Your saved views: each view's name, its period and the account IDs of the people in it. Only you can see them.
Which saved view you had open, so the tab can reopen on it. Nothing is stored for Current.
No log of who you looked at. OnTask writes no log line about whose time you viewed, and it does not tell anyone that you looked. Your saved views, and which one you had open, are the only record of whom you chose. Only you can see them.

Delete my OnTask data, under Settings & privacy, deletes your saved views along with everything else OnTask holds about you, and takes you out of the views colleagues saved with you in them. If OnTask cannot finish taking you out of someone's view straight away, it retries in its daily run until it is done. The full picture is in Data & privacy.

For site administrators

The Team tab is on for every site, and OnTask has no setting to turn it off. Anyone with OnTask on your site can see the time colleagues logged, within their own Jira permissions.

Your organisation is the controller of this data. Looking at colleagues' logged time is workplace monitoring. Your organisation needs a lawful basis for it, and must tell its staff where the law requires it. See Data & privacy.