Introduction to Organizing Work

An hour on its own answers nothing. The useful questions are who did the work, who it gets billed to, and which part of the business it belongs to. JetTime answers those three ways — with Teams, Accounts, and Workstreams. Each one groups the same hours differently, and each comes with its own worksheet (what other tools call a timesheet) and its own access rules. You'll find all three in the JetTime menu, next to My Work and Reports.

What Each One Slices By

• Team — who did the work. A team is a group of people, and each member belongs to it under a function role: Developer, Designer, QA, Account Manager, whatever your company runs on. The person logging work picks the team and the role they worked under, and both are recorded on the work log. That is what lets a report split one person's hours across the roles they actually play.
• Account — who it is billed to. An account is a client, an internal department, a project, or a cost center. It is picked on the work log as well, and it is the field you filter or group a report by when it's time to invoice.
• Workstream — everything else, by any rule you need. A workstream has no field on the Log Work form and nobody picks it. You give it a scope — conditions over work-item and work-log fields — and every work log that matches belongs to it. All bug work across every space; everything logged by the development team to the CapEx account; every hour on a client's account under the QA function role. Where a team answers one question and an account answers another, a workstream answers the rest: combine the fields that define the slice and the matching hours gather in one place, without changing how anyone logs.

They Coexist on One Work Log

The three don't compete. One work log can be logged by the Mobile team under the QA function role, billed to a client account, and still land in a "Bugs" workstream because the work item is a bug. Teams and accounts are chosen by the person logging; a workstream matches on its own and keeps matching, so widening its scope pulls in work that was logged months ago.

What All Three Give You

• A worksheet of its own. Every team, account, and workstream has a Worksheet tab — the same reporting you use in Reports, with grouping, columns, totals, time formats and export, already filtered to that one team, account or workstream. No report to build first: open it, pick a date range, and read its hours.
• Its own access. Each of the three has an Access tab where you attach a permission scheme and hand out permission roles, so the right people can see and manage that team's or that client's hours and nobody else can. The model is explained in Managing App Permissions.
• Archiving instead of deletion. Set the status to Archived and it drops out of new logging and out of access, but history survives: reports still group and filter by it.

Next Steps

Read Teams and Function Roles for the people side, Accounts for the billing side, and Workstreams for everything that needs a rule instead of a picker.