How to Track Developer Hours Against Azure DevOps Work Items

To track developer hours against Azure DevOps work items, install TimeTrack, a free QServices extension that adds a time-entry panel directly inside every work item. Developers log a date, hours, and an optional note inside ADO; entries accumulate per item with no external timesheet tool needed.

What you need before you start

Confirm the following before installing TimeTrack. See our Azure DevOps guides hub for related project setup topics.

• Azure DevOps organization admin rights: Required to install any extension from the Visual Studio Marketplace. Standard project members cannot complete the install. If you do not hold org admin access, identify who does before starting.
• An active Azure DevOps organization: TimeTrack is an ADO extension and works inside Azure DevOps only. It does not integrate with GitHub Projects, Jira, or other issue trackers.
• Visual Studio Marketplace access: Your org admin must be able to reach marketplace.visualstudio.com. Corporate firewalls occasionally block Marketplace traffic; confirm access before starting.
• Developer ADO accounts: Each team member who logs hours needs a standard ADO user account and access to the relevant project. No elevated role or special license is required for daily time entry.
• Work items already created in ADO: TimeTrack logs time against existing User Story, Task, or Bug items. If your team starts work before creating ADO items, establish that habit first or time entries will be missing from the start.

No server, external database, configuration scripts, or service endpoints are needed. TimeTrack is completely free with no per-user fee and no subscription tier.

Step-by-step: Track developer hours in Azure DevOps

The following five steps take your team from extension install to a working time-tracking practice inside ADO.

1. Install TimeTrack from the Visual Studio Marketplace (one-time org admin action). Open the TimeTrack listing on the Visual Studio Marketplace, click Get it free, and sign in with the account that holds organization admin rights. Select your ADO organization from the dropdown and confirm. The full process takes under 5 minutes. No external databases, service endpoints, or configuration scripts are created during install.
2. Confirm the time-entry panel appears on User Story, Task, and Bug work items after install. Open any of these work item types in your ADO project. A time-entry panel should appear automatically in the work item detail view. If it does not appear, check two things: first, confirm the extension was installed against the correct ADO organization; second, verify in the extension management settings that your project has been granted access. Installs can take a minute or two before the panel populates.
3. Each developer logs hours against the work item they are working on. Inside the work item, the developer selects a date, enters the number of hours, and optionally adds a short description of the work done. The entry auto-associates with the work item ID and the developer's ADO identity. No separate login, manual ID entry, or system link is required. Logging at the end of each working session rather than batching entries weekly keeps the data accurate.
4. Let entries accumulate per work item and per developer with no parallel timesheet to maintain. Multiple developers can independently log against the same work item. Entries build inside Azure DevOps itself over the life of a sprint. There is no spreadsheet to update, no database to back up, and no secondary system to keep in sync with the ADO board.
5. Review aggregated effort alongside ADO task and sprint data. Because time entries live inside Azure DevOps, you can view hours in the same context as work item status, assignee, and sprint assignment. Use this data alongside ADO's existing queries and board views to compare actual effort against original estimates. This comparison is most useful during sprint retrospectives and for improving future sizing accuracy.

What gets stored and where

Teams with data residency requirements or internal audit obligations often ask exactly where TimeTrack data lives before approving a marketplace extension. Here is a direct breakdown:

Your time data inherits the same access controls, backup schedule, and compliance posture as the rest of your ADO organization. You do not need a separate vendor agreement or data processing addendum, because TimeTrack does not move data outside your existing Microsoft tenancy.

Where this gets tricky

TimeTrack logs time against ADO work items only. Any effort that never becomes a User Story, Task, or Bug in Azure DevOps will not be captured. This is the most common gap teams hit after install, and it is a process problem rather than a tool problem.

Situations that produce missing time entries:

• Off-board work: exploratory spikes, architecture sessions, or planning done in meetings before a work item exists in ADO
• Overhead time: stand-ups, code reviews, on-call hours that the team does not model as ADO work items
• Retroactive logging: developers who try to log hours after a work item has been closed or deleted may find the entry panel unavailable depending on your ADO project configuration
• Work planned outside ADO: teams that plan in Confluence, Notion, or Slack threads first and create ADO items later will have gaps for the planning period

The practical fix is a team agreement: create the ADO work item before starting the work, not after. Teams already running their boards from ADO will find this natural. Teams that work off-board first will see gaps in time data until the habit changes.

One additional limit to know: TimeTrack does not provide built-in aggregate reports or dashboards. Reviewing individual work item entries is straightforward, but producing a view of total hours per developer per sprint requires either exporting the extension data or building a custom ADO query, Power BI report, or a more advanced Azure-based integration.

How QServices can help

TimeTrack is built and maintained by QServices and is available free directly from the Visual Studio Marketplace. No contract, support ticket, or professional services engagement is required to install or use it.

If your team needs more than individual time entry — sprint velocity dashboards, automated work item creation from meeting transcripts, or AI-assisted capacity planning tied to ADO data — QServices builds those systems on Azure. As one example, we built a Smart PM Assistant for an IT services company that captured meeting transcripts through Fireflies.ai, automatically created ADO work items with Fibonacci story point assignments, and replaced manual task allocation with real-time Power BI sprint velocity dashboards.

For related Azure DevOps and engineering operations topics, browse the full guides collection.

Do I need admin rights to install TimeTrack?

Yes. Installing any extension from the Visual Studio Marketplace requires Azure DevOps organization admin rights. This is a one-time action: once the admin installs TimeTrack for the organization, all developers in any project within that organization can log time without needing admin access themselves. Standard project member access is sufficient for daily time entry.