Time Log Summary

Time Log Summary answers the question every stand-up, invoice and sprint review runs into: who logged what, against which work item, in which week?

Choose a range, a project or several, a team and a user, then Search. The project filter opens on the project you are in and takes as many as you need, with the team and user lists following your choice; organisations with a single project do not see it, since there is nothing to choose. The range is one dropdown — This week, Last week, Last 2 weeks, Last 3 weeks, This month, Last month, Last 2 months, or any custom from/to dates. The Range total for everything on screen sits right beside the buttons, and Export downloads the full result as CSV for your own spreadsheets, invoicing or data warehouse, with each entry’s parent and the story, feature and epic it rolls up to.

• A week at a glance, a month when you need it — days run across the columns beneath the week they belong to. Click a week heading to collapse it to a single total, click again for the daily breakdown, so a two-month range stays as readable as a single week.
• Group it your way — User, Project, Area path, Iteration, your process’s backlog levels (Epics, Features and Stories, say), Parent item, Work item and Type are chips you can tick, untick and drag into any order. The grid regroups instantly, so the same search answers “what did this team spend on that epic?” and “how much of the month went to meetings?” without searching again.
• Roll time up your backlog — the backlog levels come from each project’s own setup and carry its names: Epics, Features and Stories on the Agile process, Epics and Issues on Basic, plus any level your organisation has added. Time lands under the right feature whatever it was logged against — a task under a story, a bug straight under the feature, or the feature itself — and time with nothing on a level above it is gathered under No Feature, No Epic and so on. A search across projects on different processes groups same-named levels together. Parent item still groups by whatever sits directly above.
• Save grouping — stores your arrangement against your Azure DevOps account, so it follows you to any browser or machine and is waiting for you next time. A backlog level is saved by its place in the backlog, counted up from the stories, so in a search whose projects have fewer levels the same chip can name a different one: Features saved while searching an Agile project groups by Epics in a search of Basic projects alone.
• Straight through to the work — rows carry the real Azure DevOps work item type icon and link to the item itself, custom types included. Work items that have since been deleted still let you clear up the time log entries they left behind.
• Keep digging — View Dashboard carries the filters you already set into the Analytics Dashboard, and My Time Log jumps to your personal timesheet.

Team leads get the whole team in one grid: expand a person down through their projects, work items and time types, or collapse them back to a single weekly total.