Reporting on Teams and Roles
Break down logged hours by team and by the role they were worked under.
Every work log records the team it was logged under and the function role the person worked under. Both are ordinary report fields, shown as Team and Role, so the same hours can read as one team's output or as a breakdown by role — all the development hours on one line, all the design hours on another, whoever worked them. That second view is the one an invoice is built from, because a rate usually belongs to the role rather than to the person.
How to Build the Report
Open a report in the Reports section, or create a new one.
Open the customization panel and use Team and Role as you would any other field:
- Time Grouping: add either one to break the hours into sections — per team, per role, or one nested inside the other.
- Columns: add either one to show the team and the role on each work log row.
To narrow the report instead of splitting it, click Add Filter, pick Team or Role, and choose the values you want.
Set the Date Range and build the report.
Grouping by Role
Group by Role and every hour lands under the role it was worked in, whoever worked it. All the development hours total on one line, all the design hours on another — which is exactly the shape of an invoice when each role bills at its own rate.
The hours are attributed by what the work log carries, not by anyone's job title. So a person who spent Monday as a Project Manager and the rest of the week as a Developer contributes to both lines, with the right hours in each — and nobody's time is billed at the wrong rate because of the title on their profile.
JetTime gives you the hours per role and stores no rates; you apply each rate wherever you invoice. When you need a money figure inside JetTime, that comes from a currency work log field instead — see Reporting on Costs and Financial Data.
Grouping by Team
Group by Team and you get a team's own output, across every space and every work item, no matter who logged where. Jira answers "how much time went into this space"; this answers "how much did this team do", which is rarely the same question.
Nest a second dimension under it to go further: Team → Work Log User for who contributed what, Team → Space for where a team's month went, Team → Role for the mix of work inside it.
Filtering by Team and Role
A filter narrows the report instead of splitting it: one team's hours only, or only the hours worked as a QA. Pick several values in one filter and any of them matches, so Role set to Developer and QA gives you both, and nothing else. See Using Filters in Reports.
Combining Team, Role, and Account
The two axes combine with Account, which is the report most service companies actually want. Filter by Account to pin the report to one client, then group by Role: the result is a line per role with hours against each — the shape of an invoice, ready to price.
Turn it around and it answers the other question: group by Team, then by Account, to see which clients a team spent its month on.
An Object's Own Worksheet
When you want one team's numbers and nothing else, you don't need to build a report. Every team has a Worksheet tab with the same reporting already filtered to it, which starts out on a Role → Work Log User → Space → Work Item breakdown. Accounts and workstreams have the same tab. See Teams and Function Roles, Accounts, and Workstreams.
Build a report instead when you need more than one object at a time, your own filters, or a breakdown that crosses teams and clients.
Past Hours Keep the Team and Role They Were Logged Under
Team and Role are recorded on the work log at the moment the work is logged. Reports read what was stored, not who is in which team today. So someone who has since moved to another team, picked up a different function role, or left the company still reports under the team and role they worked under back then, and a rebuilt report of last quarter shows the same numbers it always did.
Archiving a team keeps that history readable too: it stops being offered for new work, but its past hours stay in reports under its name.
Next Steps
To see how the values get onto the work log in the first place, read Logging Work for Teams. For the rest of the report builder, see Customizing Reports and Reporting on Accounts.