ADO Time Tracker
User Guide
Everything you need to get the most out of ADO Time Tracker — from logging your first time entry to running approval workflows and exporting reports, all without leaving Azure DevOps.
Overview
ADO Time Tracker adds a ADO Time Tracker tab to every ADO Work Item form plus a full-featured hub accessible from your project sidebar. Time entries are stored in the ADO Time Tracker service, scoped to your Azure DevOps organisation, so they are shared across your whole team.
The extension covers the complete time management lifecycle — from logging individual hours on work items, to weekly timesheet management, through manager approval workflows, and detailed reporting — all without leaving Azure DevOps.
Key areas
Logging time on a work item
Open any Work Item in ADO and click the ADO Time Tracker tab to view and manage all time logged against that item.
What you see
| Section | Description |
|---|---|
| Total Hours | Sum of all time logged against this work item |
| Work Item Breakdown | Hours per work item in the hierarchy |
| Team Breakdown | Hours per team member with a progress bar |
| Activities Breakdown | Hours split by activity type |
| Time Log List | Every individual entry — date, duration, comments, and who logged it |
Adding an entry
- Click Add Time to open the side panel.
-
Fill in the entry details:
- Duration — type
HH:MMor use the quick-add buttons (0.5 h, 1 h, 2 h, 4 h). - Date — defaults to today.
- Task — shown when you log on a story, PBI, feature, or epic: pick the child task the work belongs to (type to search by ID or name). The entry stays on the parent item and is credited to the task.
- Start / End time — optional; changing either auto-recalculates the duration.
- Activity Type — the list configured by your admin (custom types, or the ADO activity picklist by default).
- Line Property — Billable / Non-Billable (or Productive / Non-Productive depending on your project type).
- Internal Comment — visible to the team.
- External Comment — visible to clients.
- Reason code — only shown when the D365 F&O sync add-on is enabled for your organisation.
- Duration — type
- Click Save.
Editing & deleting entries
- Click the pencil icon on any row in the Time Log List to reopen the panel in edit mode.
- Click the trash icon and confirm to delete an entry.
- You can only edit or delete your own entries, and only in unlocked weeks.
Automatic effort fields
When your administrator has switched on effort sync, you no longer need to type values into a work item’s Completed Work and Remaining Work fields — and you should no longer do so. ADO Time Tracker calculates both fields for you from the time you log. Record your time in the tracker and the work item’s effort fields update automatically.
For administrators: switching it on
Effort sync is off until an administrator turns it on in Settings → Time Tracking → Sync logged time to work-item effort fields. It writes to Completed Work, Remaining Work and Original Estimate, and Azure DevOps processes don’t include all of them on every work item type (Scrum Tasks have only Remaining Work). Add any that are missing first. You need permission to edit your organisation’s process.
- Add the fields to the Task type. Go to Organization settings → Boards → Process, open your project’s process, then Task → Layout. Click New field → Use an existing field, pick Completed Work, place it in the Planning group and click Add field. Repeat for Remaining Work and Original Estimate if the Task doesn’t already show them.
- Add the fields to your backlog item type Optional — only if you also want the time rolled up onto the parent item (Product Backlog Item, User Story, Requirement or Issue). Open that type → Layout and repeat step 1. If you skip this, only Tasks are updated.
- Add an Original Estimate to every work item. Fill in Original Estimate (hours) on each Task you’ll log time on, and on backlog items too if you did step 2. Remaining Work is calculated from it; without an estimate, only Completed Work is updated.
- Turn on effort sync. Keep the default field references and switch Sync logged time to work-item effort fields on.
- Check it. Log 1 hour on a Task with an Original Estimate of 8. It should show Completed Work 1 and Remaining Work 7.
What gets calculated
Whenever you add, edit, or delete a time entry, these fields update on the Task, and on its parent Product Backlog Item (PBI) when your administrator added the fields there too:
| Field | How it is calculated |
|---|---|
| Completed Work | The total time logged. On a Task it is the time logged on that task; on a PBI it is the sum of all its tasks. |
| Remaining Work | Original Estimate − Completed Work, never below 0. |
| Original Estimate | Not changed automatically — you or your lead still set the estimate as usual. |
8h. You log 3h
today → Completed Work = 3, Remaining Work = 5.
Log another 2h tomorrow → Completed = 5,
Remaining = 3.
How to log time so the fields update
Both routes feed the same automatic calculation.
-
On the work item — open the work item, click the ADO Time Tracker
tab, then Add Time. Enter the duration (for example
1:30, or use the 0.5 h / 1 h / 2 h / 4 h quick buttons). If you are on a PBI or story, pick the Task the work relates to — you can type to search by task ID or name. Set the date, activity type and billable flag, add comments if you want, then Save. See logging time on a work item for the full field list. - From the weekly timesheet — open ADO Time Tracker → Timesheet in your project sidebar, pick the week, and click a day cell on the work item you worked on. See timesheet for details.
Your entry appears in the time log and the work item’s Completed Work and Remaining Work update within a couple of seconds.
Why effort is calculated for you
- Accuracy — effort reflects the time people actually logged, not manual guesses.
- Consistency — everyone’s Completed and Remaining Work is calculated the same way.
- Less double entry — log time once and the work item fields fill in for you.
- Trustworthy reports — because the numbers cannot be casually edited, roll-ups and dashboards stay reliable.
Frequently asked questions
| Question | Answer |
|---|---|
| I can still see the Completed Work and Remaining Work fields — can I edit them? | You can see them, but do not edit them. Any manual change is automatically replaced by the calculated value. Change the numbers by logging time, not by typing in the field. |
| I typed a value and it changed back on its own — is that a bug? | No, that is the automatic correction working as intended. The fields always reflect your logged time. |
| Do I still set the Original Estimate? | Yes. Original Estimate is yours to set. The tracker only fills Completed and Remaining Work. |
| I logged time but the field did not change on the open form. | Azure DevOps does not always live-refresh the form. Refresh the work item, or reopen it, and you will see the updated values. |
| I logged time on a PBI — why did a task’s numbers change? | When you log on a PBI you pick a child task, so your time is credited to that task. The PBI’s Completed Work then rolls up all of its tasks. |
| What if I made a mistake in a time entry? | Edit or delete the entry in the time log using the pencil or trash icons — the effort fields recalculate automatically. Entries in a submitted or approved week are locked, so recall the submission first. |
| A completed or closed item shows 0 remaining work. | That is expected — closed items always have 0 remaining. Completed Work still shows the total logged. |
Quick summary
- Log all your time in ADO Time Tracker, either on the work item or in the timesheet.
- Never hand-edit Completed Work or Remaining Work — they are calculated for you.
- Keep setting Original Estimate as normal.
- Need to correct effort? Fix the time entry, not the field.
Timesheet
The Timesheet page is the primary weekly grid for viewing and editing time across all your work items at once.
Layout
- Rows — work items organised in a Project → Work Item Type → Work Item hierarchy.
- Columns — one per day of the selected week, plus a weekly total column.
- Header — shows the week date range, week total, and the Week Status control.
Navigating weeks
Use the ← / → buttons in the header to move between weeks, or click Current Week to jump back to today’s week.
Entering time
Click any cell in the grid to open the Quick Entry dialog. It pre-loads all existing entries for that day and work item so you can edit them in one place. Saving replaces whatever was stored for that cell.
Filters
| Filter | Effect |
|---|---|
| Current Project | Show only work items in your current ADO project |
| Flat view | Hide the hierarchy and show only work items you have logged time to |
Expand / Collapse
Use the + and − buttons in the toolbar to expand or collapse all hierarchy levels at once.
Approval status badges
Each work item row shows a coloured badge indicating the approval state of that week’s time:
| Badge | Meaning |
|---|---|
| Draft | Not yet submitted |
| In Review | Submitted, awaiting approval |
| Approved | Approved by a manager |
| Rejected | Rejected — a comment explaining the reason appears in the tooltip |
Locks are per row: only rows that belong to a pending or approved submission are locked. After a rejection the rejected rows become editable again — correct them and Resubmit directly from the badge. Rows that were already approved keep their approval.
Approval Workflow
Once you have finished logging time for a week, submit it to a manager for approval. The submission locks the week and creates a traceable audit trail of every status change.
Submitting a week
- Open the Timesheet page for the week you want to submit.
- Click the Week Status badge (e.g. "In Progress").
- Select Submit for Approval.
- Choose an Approver from the list and confirm. Only users who hold the Approver or Global Approver role appear here.
Your week is now locked and the status badge changes to Submitted for Approval.
Viewing approval history
Click the Week Status badge → View Approval History to see a full timeline of submit, approve, and reject events — including timestamps and reviewer names.
Resubmitting after a rejection
Rejected rows unlock automatically. Fix the entries, then click the badge and choose Resubmit. Rows the approver already approved are carried forward unchanged, so only the corrected work items go back for review.
Approval Page (Managers)
Three-panel layout
| Panel | Description |
|---|---|
| Left | List of pending, unsubmitted, and archived weeks |
| Middle | All submissions for the selected week — one row per team member |
| Right | Hierarchical timesheet detail for the selected team member submission |
Reviewing a submission
- Select a week from the left panel.
- Select a team member’s submission from the middle panel.
- Review the full breakdown of their logged hours by project, work item type, and work item in the right panel.
Available actions
- Approve or Reject the entire submission — a comment dialog appears on rejection.
- Approve or Reject individual work items within the submission for granular control.
- Bulk approve multiple submissions at once using the checkboxes in the middle panel.
Reporting
The Reporting page provides charts, summary cards, and a detail table you can filter and export.
Filters
| Filter | Description |
|---|---|
| Date range | Preset options (Today, This Week, Last Week, This Month, etc.) or a custom range |
| Projects | One or more ADO projects |
| Users | One or more team members |
| Work Items | Search by title or #ID |
| Activity Types | Development, Testing, Meeting, etc. |
| Line Property | Billable, Non-Billable, Productive, Non-Productive |
| Work Item Types | Epic, Feature, Story, Task, Bug, etc. |
Filters cascade — selecting a project automatically updates the available user list.
Summary cards
The top of the page shows six at-a-glance cards: Total Hours, Billable Hours, Non-Billable Hours, Projects, Users, and Work Items.
Charts
- Hours by Day — bar chart showing daily totals across the selected period.
- Breakdown (pie / donut) — proportion by the selected group-by category.
- Breakdown (bar) — the same data as a stacked or grouped bar chart.
Detail table
- Columns: Date, Work Item, User, Hours, Activity, Line Property.
- Click any column header to sort.
- Use the Group by dropdown to roll up rows by Date, Week, Project, User, Work Item, Work Item Type, or Activity Type. Grouped rows are expandable.
Export
Click Export CSV to download the current filtered and grouped data as a spreadsheet — ready for billing, payroll, or stakeholder reporting.
Settings
Time tracking
| Setting | Description |
|---|---|
| Working hours / day | Slider 1–24 h, used for utilisation calculations and the daily cap |
| Weekly cap | Maximum hours per week before a warning is shown |
| Enforce Time Caps | When on, an entry that would exceed the daily or weekly cap is blocked instead of just warned |
| Require Task selection | Time logged on a story, PBI, feature, or epic must be attributed to one of its child tasks (on by default) |
| Require “In Progress” state | Time can only be logged on work items whose state is in the In Progress category (Active, In Progress, Doing, or your process’s equivalent) |
| Prevent self-approval | Approvers cannot approve or reject their own timesheet |
| Working days | Toggle individual days (Mon–Sun) to match your team’s schedule |
| Sync logged time to work-item effort fields | Master switch for effort sync, plus the Completed Work, Remaining Work, and Estimate field references used for tasks and for parent items (see Automatic effort fields) |
Time entry rules
Choose which work item types accept time, per ADO process (Agile, Scrum, CMMI, or any inherited process). Pick a process, then tick the types — every project on that process follows the rule. A process with no types ticked allows all types. The list shows the process’s requirement backlog level by default; switch off Show only … types to see every type.
Activity types
By default the Activity dropdown uses your ADO activity picklist. Add your own names here to replace it with a custom list, or import the ADO list as a starting point and edit it. Existing entries keep the activity they were saved with.
Users & roles
Manage who has access and what they can do:
- Add User — pick a member of your Azure DevOps organisation and assign one or more roles: Administrator, Approver, Global Approver, Timesheet User.
- Edit / Remove existing users at any time.
- Anyone who should review timesheets needs the Approver role (or Global Approver to review every submission). Only role holders appear in the submit dialog.
- Role badges are colour-coded (see Roles & Permissions below).
Data management
| Action | Description |
|---|---|
| Export Data | Download all extension data as a JSON file for backup or migration |
| Factory Reset | Permanently delete all settings and time logs — type RESET to confirm. This action cannot be undone. |
Account
Shows the signed-in user and the roles assigned to them.
Integrations (add-on)
The D365 F&O section appears when the Dynamics 365 Finance & Operations sync add-on is enabled for your organisation. Admins connect the F&O environment, map projects and categories, and review sync diagnostics here. Contact sales@defactoinfotech.com to enable the add-on.
Weekly or daily sync. Under Sync granularity, choose Weekly to send each approved week as one F&O timesheet, or Daily (Dataverse route) to let each person sync their own days. With Daily on, the Timesheet page shows a Sync day → F&O button: pick a day and it becomes its own single-day F&O timesheet, with no approval needed. Syncing the same day again replaces the earlier timesheet, and if an entry has no category the message lists it so you can fix it and sync again.
Activity. With the add-on on, every time entry form shows an Activity field listing the F&O activities of the work item’s project. The activity that matches your work item is selected for you; if none matches, the project’s default is selected and you can change it. The sync books the entry to the activity you chose. Once a day’s timesheet has been submitted in F&O, syncing that day again is refused until it is recalled in F&O, so a timesheet that is in review is never changed.
Roles & Permissions
ADO Time Tracker uses four built-in roles. Each user can hold one or more roles depending on their responsibilities within the team.
| Role | What they can do |
|---|---|
| Admin | Full access: settings, time entry rules, users and roles, and data management |
| Global Approver | Approve / reject any team member’s timesheet |
| Approver | Approve / reject timesheets for their assigned team members |
| Timesheet User | Log, edit, and submit their own time entries |
Ready to start tracking time?
Install ADO Time Tracker from the Azure Marketplace in under 3 minutes — no credit card, no external tools, no context-switching required.
No credit card required · Azure DevOps Cloud & Server · v3.67
