Feature burndown
Estimated, spent and remaining hours per Feature, a day-by-day burndown with a working-day forecast,
who is logging time on what, and the bugs raised — read live from Azure Boards as the signed-in user.
Azure DevOps has burndowns for sprints, not for Features, and none over custom hour fields. This hub
adds one under Boards → Feature burndown.
What you see
All open features (landing page)
- Hours logged per day over the last four weeks, stacked by feature
- Who worked on what: closed tasks for any day of the last week, grouped by developer
- A sortable table: status (late / stalled / on track), estimated, spent, remaining, PBIs done,
unestimated hours, open bugs, hours in the last 7 days, target and forecast dates
One feature
- Tiles: estimated · spent · remaining by state · remaining by hours · development done · forecast ·
unestimated work · open bugs and defects
- Burndown: scope, remaining (by state and by hours), spent, ideal line to the target date, and a dashed
projection at the last four weeks' pace — sprint bands, hover for any day
- Hours logged per day by work type or by developer
- Team, last-7-days summary, PBI table with variance, open bugs and defects, hours logged outside any PBI
How it reads your process
The hub adapts to the project at load and says so in its header:
| Concept |
Looked up as |
| Parent |
Feature, else Epic |
| Story |
Product Backlog Item, User Story, Requirement or Issue |
| Estimate (hours) |
Custom.Initialestimation, Custom.Estimation, Original Estimate, Effort or Story Points — whichever carries data |
| Hours spent |
Custom.ActualEstimation, Custom.Actualestimation or Completed Work on Done tasks |
| Development done |
story states in the Resolved or Completed category (plus Submitted / Ready for test / Testing) |
| Bugs |
Bug and Defect work items under the feature |
Hours spent are attributed to the nearest story above the task; tasks that are not Done are excluded
and reported. Days are calendar days in IST; forecasts count Monday–Friday only.
Privacy
Everything runs in your browser with your own Azure DevOps sign-in (vso.work read scope). No data
leaves Azure DevOps; revision history is cached in your browser only, to make later opens faster.
Requirements
A Scrum-style process with Feature → story → Task hierarchy links. Hour fields on stories and tasks
(see the table above); without them the report still shows scope and state, with spent hours at zero.
| |
