Media
2 items
Description
Watches Azure DevOps time-field edits and generates a daily standup message. Azure Standup turns the hours you already log on Azure DevOps work items into the daily standup message you have to send your team leader. If your team asks for an end-of-day summary listing every task you touched, its work item ID and the hours you spent on it, you know the routine: scroll back through the tasks, try to remember which ones you edited, work out how much you added to each weekly bucket, then type it all out. Azure Standup does that bookkeeping for you. HOW IT WORKS Connect your Azure DevOps organization once with a read-only access token. From then on, open the popup and click Sync day. The extension reads your own work item history for that day through the official Azure DevOps REST API, works out how many hours you added, and lists each task with its hours. Your standup message is generated underneath, ready to copy with one click. IT RECORDS THE CHANGE, NOT THE TOTAL This is the part that matters. Time fields in Azure DevOps usually hold a running weekly total, so if a field goes from 5 to 10, you spent 5 hours today, not 10. Azure Standup always records the difference. Corrections made later the same day are folded into the net, so changing a value from 0 to 3 and back to 0 contributes nothing, and 3 to 7 contributes four hours. When it cannot tell what a field held before your edit, it says so instead of guessing: the row is flagged and you confirm or correct the number before copying. IT FINDS YOUR FIELDS BY ITSELF Every Azure process names its custom time fields differently, and the labels you see on the form are not the names stored underneath. Azure Standup builds a list of the time fields it actually sees in your organization and you tick the ones you want tracked. Nothing is hardcoded, so it works with an inherited process, a custom one, or several projects at once. Dev and testing time are kept apart, so hours logged against a testing field never get silently merged into your development total. THE MESSAGE IS YOURS TO SHAPE Both templates are editable. The per-task block takes tokens for project, area, work item ID, title and hours; the surrounding message takes tokens for the task list, the day total and your notes. Write your greeting in any language, reorder the lines, or drop fields you do not need. Project aliases let you show a client-facing project name instead of the internal one. The finished message appears in an editable box, so you can adjust the wording before copying without going back to change the template. WHAT ELSE IT DOES - Pick any past date to pull up that day's entries, kept as long as you keep the extension - Edit any row's hours by hand; your correction is never overwritten by a later sync - Add a notes or issues line per day, with a default you set once - One organization covers every project you can access, configured in a single step PRIVACY There is no account, no server and no analytics. Your access token, your settings and your day history are stored only in this browser profile using Chrome's local storage. The extension talks to exactly one place: your own Azure DevOps organization. Nothing is sent anywhere else, and nothing is shared with the developer or any third party. The token only ever needs Work Items (Read) scope, so the extension cannot change anything in Azure DevOps. You can remove it from the browser at any time from the Settings tab. REQUIREMENTS - An Azure DevOps Services account at dev.azure.com. On-premise Azure DevOps Server is not supported. - A personal access token with Work Items (Read) scope, which you create in your own Azure DevOps user settings. - Custom or built-in numeric time fields on your work items, which you select in the extension's Settings tab.