Can't see progress towards a milestone, so people use burndown charts elsewhere
Often a milestone is targeted at a particular date, but it is not easy to see whether targeted tasks are on schedule for that date.
Unfortunately, this causes a lot of bureaucracy in copying or linking issues from bug reports to blueprints. To the extent that developers don't get around to doing that copying or linking, bug fixes are implicitly deprioritized in favor of features, lowering the software's quality. And time is lost when people don't know about the burndown chart, or have trouble finding it.
This could be fixed in Launchpad by providing a Burndown view of bug reports, as a toggle with the existing List view. (See also bug 914854, about providing a Kanban view for a team.)
Implementing this would require first implementing a bug listing for milestones. <https:/
|Changed in launchpad:|
|status:||New → Triaged|
|importance:||Undecided → Low|