Start a timer on the work item and TicTask does the rest: Completed Work, Remaining Work and the task state stay up to date, with a record of who logged how much and when.
The extension is private: an access request shares it with your organization. The extension and its docs are in Portuguese. Open source, MIT license.
Everything inside Azure DevOps, with no server of its own: the data lives in your organization's Extension Data Service.
Start, pause and complete right on the Task. Pausing already logs the time and takes it off Remaining Work: nothing is left pending.
When pausing, say why (waiting for review, helping a colleague, meeting). When completing, the next step (sent for review, PR approved). It all goes to the task discussion and, when it matters, to the story's.
On the User Story or Bug, pick one of your tasks or create a new one from a description: it is assigned to you, with the story's area and iteration, and the timer starts on it.
Your day at a glance: the running timer, today's and this week's hours, paused tasks with the reason and how many days they have been waiting, and today's entries as a tree.
Hours by day, week or month, per person, story, task and activity, with PDF and CSV export. In the calendar, drag to log time or fix the hours.
The task state tells who is working on it. Completed Work is the sum of the entries, each entry takes off Remaining Work and everything stays in the work item history.
An organization administrator does this once. The full guide is in the wiki (in Portuguese).
Open a request with your organization name. It gets shared with you and updates arrive on their own.
In Organization settings › Extensions › Shared, install TicTask.
Add the Stopped state to the Task if it doesn't exist. See how.
In Boards › TicTask › Settings, review activities, states and reasons.
No. Entries live in Azure DevOps' own Extension Data Service, and the hours go to the work item fields.
With Agile, Scrum and inherited processes. The process needs a pause state on the Task (Stopped by default), and the types and states are configurable.
No. TicTask measures the effort on each task. Pausing means leaving the task for now (another task, a meeting, end of day), not a coffee break.
Yes, from the CSV exported on the Time Log Admin page, without changing the work items. See how.
Everyone sees their own. Managers (team administrators and configured e-mails) see the whole team and who has a timer running.
TicTask